Security | Authorization
Authorization requests are requests by a user or customer for certain permission grant. Please check type definitions for current supported cases.
Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.
Filter by one or more requesting company ids.
Filter by one or multiple specific types
Filter by one or multiple specific statuses
Filter the requests created after the specified date.
Sort the requests by a given criterion
Order in which the result of a list request is sorted.
Specifies the index of the first item to return
0Specifies the maximum number of items to return (min: 1; max: 1000)
100OK: A list of authorization requests.
Bad request: See response message for details.
Unauthorized: Invalid api key.
Forbidden: Resource access denied or resource does not exist anymore.
GET /v1/security/authorization-requests HTTP/1.1
X-API-KEY: YOUR_API_KEY
Accept: */*
{
"previous": {
"href": "text",
"method": "text"
},
"next": {
"href": "text",
"method": "text"
},
"items": [
{
"requestingCompany": {
"id": 83,
"name": "equipme GmbH",
"self": {
"href": "text",
"method": "text"
}
},
"approvingCompany": {
"id": 83,
"name": "equipme GmbH",
"self": {
"href": "text",
"method": "text"
}
},
"creator": {
"id": 1,
"firstName": "Pierce",
"lastName": "Bell",
"fullName": "text",
"email": "p.bell@foo.io",
"username": "j.doe@foo.inc",
"costCenter": "4645-2343",
"costCenterId": 1,
"self": {
"href": "text",
"method": "text"
}
},
"processor": {
"id": 1,
"firstName": "Pierce",
"lastName": "Bell",
"fullName": "text",
"email": "p.bell@foo.io",
"username": "j.doe@foo.inc",
"costCenter": "4645-2343",
"costCenterId": 1,
"self": {
"href": "text",
"method": "text"
}
},
"type": "orderAuthorization",
"status": "new",
"created": "2026-01-01T00:00:00.000Z",
"completed": "2026-01-01T00:00:00.000Z",
"note": "text",
"id": 916,
"self": {
"href": "text",
"method": "text"
}
}
],
"total": 1,
"self": {
"href": "text",
"method": "text"
}
}Authorization requests are requests by a user or customer for certain permission grant. Please check type definitions for current supported cases.
Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.
A note on the authorization request. Supports html formatted text including inline css styles.
This is a <b>required permission</b>.Created: The created authorization request.
The date and time the authorization request was created.
The date and time the authorization request was completed.
A note on the authorization request. Supports html formatted text including inline css styles.
The identifier of the authorization request.
916Bad request: See response message for details.
Unauthorized: Invalid api key.
Forbidden: Resource access denied or resource does not exist anymore.
POST /v1/security/authorization-requests HTTP/1.1
X-API-KEY: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 76
{
"type": "orderAuthorization",
"note": "This is a <b>required permission</b>."
}{
"requestingCompany": {
"id": 83,
"name": "equipme GmbH",
"self": {
"href": "text",
"method": "text"
}
},
"approvingCompany": {
"id": 83,
"name": "equipme GmbH",
"self": {
"href": "text",
"method": "text"
}
},
"creator": {
"id": 1,
"firstName": "Pierce",
"lastName": "Bell",
"fullName": "text",
"email": "p.bell@foo.io",
"username": "j.doe@foo.inc",
"costCenter": "4645-2343",
"costCenterId": 1,
"self": {
"href": "text",
"method": "text"
}
},
"processor": {
"id": 1,
"firstName": "Pierce",
"lastName": "Bell",
"fullName": "text",
"email": "p.bell@foo.io",
"username": "j.doe@foo.inc",
"costCenter": "4645-2343",
"costCenterId": 1,
"self": {
"href": "text",
"method": "text"
}
},
"type": "orderAuthorization",
"status": "new",
"created": "2026-01-01T00:00:00.000Z",
"completed": "2026-01-01T00:00:00.000Z",
"note": "text",
"id": 916,
"self": {
"href": "text",
"method": "text"
}
}Authorization requests are requests by a user or customer for certain permission grant. Please check type definitions for current supported cases.
Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.
The identifier of the authorization request.
OK: The requested authorization request.
The date and time the authorization request was created.
The date and time the authorization request was completed.
A note on the authorization request. Supports html formatted text including inline css styles.
The identifier of the authorization request.
916Bad request: See response message for details.
Unauthorized: Invalid api key.
Forbidden: Resource access denied or resource does not exist anymore.
NotFound: Requested resource could not be found.
GET /v1/security/authorization-requests/{requestId} HTTP/1.1
X-API-KEY: YOUR_API_KEY
Accept: */*
{
"requestingCompany": {
"id": 83,
"name": "equipme GmbH",
"self": {
"href": "text",
"method": "text"
}
},
"approvingCompany": {
"id": 83,
"name": "equipme GmbH",
"self": {
"href": "text",
"method": "text"
}
},
"creator": {
"id": 1,
"firstName": "Pierce",
"lastName": "Bell",
"fullName": "text",
"email": "p.bell@foo.io",
"username": "j.doe@foo.inc",
"costCenter": "4645-2343",
"costCenterId": 1,
"self": {
"href": "text",
"method": "text"
}
},
"processor": {
"id": 1,
"firstName": "Pierce",
"lastName": "Bell",
"fullName": "text",
"email": "p.bell@foo.io",
"username": "j.doe@foo.inc",
"costCenter": "4645-2343",
"costCenterId": 1,
"self": {
"href": "text",
"method": "text"
}
},
"type": "orderAuthorization",
"status": "new",
"created": "2026-01-01T00:00:00.000Z",
"completed": "2026-01-01T00:00:00.000Z",
"note": "text",
"id": 916,
"self": {
"href": "text",
"method": "text"
}
}Authorization requests are requests by a user or customer for certain permission grant. Please check type definitions for current supported cases.
Required for authorization in every request. You can request an API-Key for your tenant in the integrations section of the equipme App.
The identifier of the authorization request.
NoContent: Request has succeeded.
No content
Bad request: See response message for details.
Unauthorized: Invalid api key.
Forbidden: Resource access denied or resource does not exist anymore.
NotFound: Requested resource could not be found.
PATCH /v1/security/authorization-requests/{requestId} HTTP/1.1
X-API-KEY: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 245
[
{
"op": "add",
"path": "/status",
"value": "approved"
},
{
"op": "add",
"path": "/note",
"value": "This is a <b>required permission</b>."
},
{
"op": "add",
"path": "/processorId",
"value": 123
},
{
"op": "add",
"path": "/completed",
"value": "2026-10-09T16:38:45.8527113Z"
}
]No content
Last updated
Was this helpful?