Postman Collections
Ready-to-use Postman collections for channel partners who want to test TMF onboarding and the SEP (CAMARA) APIs without writing any integration code first. Download the collection for the flow you need, import it into Postman, fill in your own credentials, and run the requests.
TMF Onboarding (App Owner + Application + Product Order)
Runs the full TMF931 onboarding flow: create an Application Owner, create an Application under that owner, then submit a Product Order for the SEP CAMARA API product you were approved for.
Sim Swap v1
Detects whether a subscriber's SIM card has been swapped recently.
Sim Swap v2
Detects whether a subscriber's SIM card has been swapped recently.
KYC Match v0.2
Checks whether subscriber-provided identity/address details match what the operator has on file.
KYC Match v0.3
Checks whether subscriber-provided identity/address details match what the operator has on file.
KYC Age Verification v0.2
Checks whether the subscriber is above a given age threshold, without revealing their exact birthdate.
KYC Fill-in v0.3
Returns the subscriber's identity/address details already known to the operator, to pre-fill a form. The subscriber is identified via the access token, not a request body field.
Location Verification v2
Verifies whether the subscriber's device is currently located within a given area.
Location Retrieval v0.4
Retrieves the subscriber's last known device location.
Device Roaming Status v1
Checks whether the subscriber's device is currently roaming.
Device Reachability Status v1
Checks whether the subscriber's device is currently reachable on the network.
Number Verification v1 (NV1)
Silently verifies that a given phone number matches the device making the request, via a network-based flow while on cellular data.
Number Verification v2.1 (NV2)
Verifies a phone number (or looks up the device's phone number) using a TS.43 operator token as the subscriber identifier instead of a phone number.
Number Recycling v0.2
Checks whether a phone number has been recycled (reassigned to a new subscriber) since a given date.
Quality on Demand v1.1
Creates a temporary network quality-of-service session (e.g. low-latency) for a subscriber's device or a network-based application.
All-in-One (every API and grant type in a single collection)
Every SEP CAMARA API above, combined into a single collection, organized as one folder per API with a
sub-folder for every grant type variant built for that API (JWT Bearer, then CIBA, then Authorization
Code, in that order, whichever exist) — fill in client_id, private_key and
optionally kid once at the top of the collection's Variables tab, and
every folder and sub-folder reuses those same shared credentials, so there's nothing to re-enter per
API or per grant type. Everything else (scope, phone numbers, and other per-API/per-grant parameters)
is namespaced per sub-folder with working defaults already filled in.
How to use a collection
Download the collection file for the API and grant type you want to test.
In Postman: File → Import and select the downloaded .postman_collection.json file.
Open the collection's Variables tab and fill in client_id and private_key (and kid if your JWKS has more than one key).
Leave base_url as Germany staging, or change it to production/another country per the Endpoints page.
Run the requests in order, top to bottom. Token requests automatically capture the access token into a collection variable for the requests that follow. For the TMF Onboarding collections, IDs from each step (owner_id, app_id, order_id) are captured automatically too.