What you get back
You receive the newly created secret API key once for secure storage in the intended system.
A typical day-to-day use case
A location connects an additional ERP module. The module receives its own key without sharing the existing production access.
The tangible business value
Access, costs and usage can be controlled centrally. A partner network can grow without losing visibility or accountability.
- Creates a visible status and clear ownership so no case gets lost between systems or teams.
- Makes uncertainty and review points visible before they become a wrong approval, order, publication or charge.
- Makes costs and decisions more transparent so budgets can be used deliberately and unnecessary work can be avoided.
Who benefits most
| Area of use | The practical advantage |
|---|---|
| ERP, DMS, shop and software providers | Embeds the capability in the system of record through an API and processes results without another manual step. |
| Platform and partner networks | Makes permissions, usage and sponsored billing manageable across connected businesses. |
How the endpoint fits your workflow
The endpoint handles one clear task and passes its result straight to the next step.
- An authorised manager decides who may use or pay for which service.
- The change is sent securely from the system of record to tapinomahub.
- Confirmation and identifiers are recorded so permissions and costs remain transparent.
When it is time to implement
Fields, examples, possible responses and prices are available in the API documentation for POST /client/users/{clientId}/keys.
Sources and legal references
Frequently asked
What do I get back from this endpoint?
You receive the newly created secret API key once for secure storage in the intended system.
Who benefits most from this endpoint?
ERP, DMS, shop and software providers, Platform and partner networks.
Where can I find the implementation details?
The directly linked tapinomahub API documentation contains fields, examples, possible responses and prices.