readmeerrors add messagedelete messageget ad typesget formatsget issue typesget keysget message typesget poster namesget solution typesget stocks attachmentmessage typemessage

Grandville Printing Company

The GPC API is organized around REST. Our API has predictable resource-oriented URLs, accepts JSON-encoded request bodies, returns JSON-encoded responses, and uses standard HTTP response codes, authentication, and verbs.

You can use the GPC API in test mode by using our development envrioment, which doesn't affect your live data.

The GPC API doesn't support bulk updates. You can work on only one object per request.

Base URL

The GPC API is served over HTTPS.

The following enviroments are available:

Authentication

The GPC API uses API keys to authenticate requests.

Test mode secret keys have the prefix gpc_test_ and live mode secret keys have the gpc_live_ prefix.

Your API keys carry many privileges, so be sure to keep them secure! Do not share your secret API keys in publicly accessible areas such as GitHub, client-side code, and so forth.

Provide your API key as the value for the key query parameter.

All API requests must be made over HTTPS. Calls made over plain HTTP will fail. API requests without authentication will also fail.