Authentication#
API is using an API Key authentication scheme that requires X-API-KEY header to be present in each request. Each API key is associated with:Environment (test or poduction, see below).
Specific PostPlus account with specific authorization rules, i.e. a given API key might be authorized to manage shipments, but not authorized to request HS codes. Authorizations are managed by PostPlus according to customer agreements.
Customer Portal#
Parcels, labels, shipments created via API can also be accessed via customer portal, see urls below in the Environments section.
IT support and customer portal related documentation is accessbile at https://postplus.freshdesk.com/support/solutionsEnvironments#
PostPlus has currently two customer-facing environments in use: test and production. Test environment suits for prototyping and integration development, it contains the latest releases that might not be available in production yet, and additionally, data in the test environment gets reset on regular basis.TEST environment#
Bear in mind, that TEST environment is a shared environment, multiple customers might use it at the same time. The data is being reset on a regular basis, so users should not expect the data to be retained there for extended periods of time.Customer Portal credentials:password: apitest1234567890
PRODUCTION environment#
Production API key and access to customer portal will be provided by the account manager.API request rate limtis#
š PostPlus API applies rate limiting to all client requests
PostPlus API applies rate limiting (normally 5 requests per seconds) to all client requests, so integrators must cosider batch operations whenever possible, for example in Tracking EndpointsSending API requests from the documentation user interface#
Sample API requests provided in the documentation use TEST environment and TEST API key by default