API: New Infrastructure

1NCE is continuously growing. With more customers on our network, securing continued stability is mandatory. As of October 25, 2021, changes to the 1NCE API and server backend were introduced to increase the overall performance and security of the Management API. These changes include the DNS record for api.1nce.com and additions to the general API behavior.

If there are any issues with the API integration, feel free to contact our 1NCE Support for technical guidance.

Below we have listed the changes that were introduced during this change, please check the list of changes for details.

• DNS record of api.1nce.com changed due to new backend.
• API Authentication:
  • API token valid for 3600 seconds (one hour).
  • New API token for every OAuth request, old API tokens stay valid until timeout.
  • Increased Bearer Token length to about 3000 chars.
  • API authentication response was extended with additional fields. See the comparative example below.
• Endpoint Rate Limiting, please see API Rate Limits Change Log for more information.
• API User:
  • Authentication for certain API user might fail if they haven't logged in for a longer time.
  • Try setting a the API user password in the 1NCE Portal.
  • Create a new API user in the 1NCE Portal.

Old API authentication JSON response:

{
    "access_token": "<37-char-token>",
    "token_type": "bearer",
    "expires_in": 1234,
    "scope": "all"
}

New API authentication JSON response with longer token and added fields:

{
    "status_code": 200,
    "access_token": "<3013-char-token>",
    "token_type": "bearer",
    "expires_in": 3600,
    "userId": "user",
    "scope": "all"
}