Environments
Testing and production hosts, and why a token or IDP client from one does not work on the other.
Develop against testing. Production traffic uses the production host only after that integration is ready.
| Testing | Production | |
|---|---|---|
| API | https://api-tst.nocfo.io | https://api.nocfo.io |
| Login | https://login-tst.nocfo.io | https://login.nocfo.io |
| Personal access tokens | login-tst.nocfo.io/auth/tokens | login.nocfo.io/auth/tokens |
| ReDoc | api-tst.nocfo.io/docs | api.nocfo.io/docs |
| OpenAPI | api-tst.nocfo.io/openapi | api.nocfo.io/openapi |
A token issued in one environment is not valid in the other. An IDP client is registered per environment too. The login settings for that client are on the login host above, at /.well-known/openid-configuration. Ask for both in the client request when you need both. Do not point a testing client id at production, or the reverse.
The public path prefix is /v1/, except POST /auth/jwt/. This site does not announce a deprecation policy. Read the operation you call in the reference before you depend on a field.
The copy of the contract on this site, openapi.json, is fetched from production when the docs are built.