API Keys and Integrations
How to create an API key, why production access must be approved, and how to request an integration.
Updated 18 August 2026
You can find everything about the API and integrations under Settings → Integrations and API. There you create API keys yourself, and from there you request the integrations we set up manually.
Create an API key
Go to Settings → Integrations and API
The address is send.glede.app/settings/api.
Press "Create API Key"
Give the key a name you'll recognize later, such as the system it's used from.
Copy the key right away
It will appear only this one time. If you close the window without copying, you must create a new one.
The key gives access to order on behalf of the company. Keep it as a password — in a password box or as a secret in your system, never in an email or shared document.
Production access must be approved
In the sandbox you can create keys right away and test freely — nothing costs money there. For production, we must approve the company first. If you try before it is in place, you will get "Request API access".
- Sandbox: create a free account at sandbox.send.glede.app and create the key there. The key begins with `sk-sandbox`.
- Production: send us a short description of what you will use the API for, and we will open access. The key then begins with `sk-prod`.
The sandbox uses the same endpoints as production. When you're ready, you just change the key and address — no code changes.
Can't create a key?
Only admins can create API keys- What it means
- Your user is a member, not an administrator. The button is visible to everyone, but only administrators are allowed to create or delete keys.
- What to do
- Ask an administrator in your company to create the key, or to make you an administrator. See Invite colleagues and choose role.
If you get "Request API access" instead, it is not your role that is listed — then the company lacks production access, as described above.
Delete a key
Press the trash can next to the key. It stops working immediately and cannot be used again — but it remains in our history, so we can see what was ordered with it. If a key is misplaced, delete it immediately and create a new one.
Documentation
The API documentation is at glede.readme.io. There you will find the endpoints for orders, templates and funding sources, as well as the setup for purchasing integrations.
Integrations we set up for you
Everything other than the API is set up manually. Choose what suits Integrations and API, and we'll get in touch:
- PunchOut — shop in Glede straight from the purchasing system. We support cXML and OCI.
- EHF catalogue — enter Glede as a catalogue in the purchasing system.
- HR system — send gifts from the HR system. We are integrated with Huma today.
- MCP — connect Glede to AI assistants via the Model Context Protocol.
The HR integration does not retrieve employees from the HR system automatically. It is the HR system that initiates the order with us — not the other way around.
Please tell us which system you are using today when you submit, and we will find the right setup right away. We usually respond within one working day.
Did this answer your question?