Skip to main content
POST /api/v1/forward/resources/registry Registers an existing resource by ID. This endpoint has upsert semantics: first registration returns 201 Created, while subsequent registration updates return 200 OK.

​
Headers

HeaderRequiredDescription
AuthorizationYesBearer <PAT>
Content-TypeYesapplication/json
Idempotency-KeyNoOptional idempotency key for unsafe requests.

​
Body parameters

ParameterTypeRequiredDescription
typestringYesResource type. Supported values: skill, file, vault, environment.
resourceobjectYesResource object. Only resource.id is used.
resource.idstringYesResource ID, such as skill_... or file_....

​
Example request

curl -s -X POST 'https://api.qoder.com/api/v1/forward/resources/registry' \
  -H "Authorization: Bearer $QODER_PAT" \
  -H "Content-Type: application/json" \
  -d '{
    "type": "skill",
    "resource": {
      "id": "skill_xxx"
    }
  }'

​
Example response

HTTP 201 Created 
{
  "id": "skill_xxx",
  "type": "skill"
}

​
Response fields

FieldTypeDescription
idstringForward Resource ID. Directly matches the resource ID.
typestringResource type.

​
Errors

HTTPTypeTrigger
400invalid_request_errorMissing or unsupported type, missing resource.id, or malformed body.
401authentication_errorPAT invalid or expired.
403permission_errorCaller has no access to the resource.
404not_found_errorResource does not exist, or declared type does not match actual resource type.

​
Notes

  • Create or update the resource through the resource API before registering it with Forward.

List resources

Create a template