TFAPI

Current Version: 1.2.1

General description

This collection contains all the tested and verified API endpoints available on the Telefakt API built and managed by the Telefakt team. As new features become available they will be tested with requests and documented here. If you have any questions regarding this contact the Telefakt team by teams or by mail.

Usage

This API exists in two environments, test and production, in each environment the API is accesible via two separate URL's. One which is only available internally, i.e. from inside the VPN and one which is availabe externally via a reverse proxy service. You can find more information about how to get credentials and configuring the use of the reverse proxy service from confluence, lookup 3scale.

Whenever you run any request other than a GET we require that you use a uuidv4 trace header, this allows us to properly log incoming request bodies and helps us when we try to debug failing requests. We also suggest that you store this trace header somewhere in your logs so you can reference that number to us. The trace should be placed in a header called X-TRACE-ID.

TLDR;

• You can use our API either internally or externaly from the URL's above.

• However you use it you will need a JWT in the Authorization header from the authentication endpoint which you can find on the reverse proxy service.

• You should also use a uuidv4 in the X-TRACE-ID header on every request other than GET requests

Servers

• https://bss-api-test-2445582745966.production.gw.apicast.io:443

• https://bss-api-production-2445582745966.production.gw.apicast.io:443