Retry File Processing

const options = {
  method: 'POST',
  headers: {
    'x-api-key': '<x-api-key>',
    'x-organization-id': '<x-organization-id>',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({event_type: '<string>', detail: {}, 'detail.file_id': '<string>'})
};

fetch('https://api.dcycle.io/v1/files/send-event', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

import requests

url = "https://api.dcycle.io/v1/files/send-event"

payload = {
    "event_type": "<string>",
    "detail": {},
    "detail.file_id": "<string>"
}
headers = {
    "x-api-key": "<x-api-key>",
    "x-organization-id": "<x-organization-id>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

curl --request POST \
  --url https://api.dcycle.io/v1/files/send-event \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --header 'x-organization-id: <x-organization-id>' \
  --data '
{
  "event_type": "<string>",
  "detail": {},
  "detail.file_id": "<string>"
}
'

POST

files

send-event

Retry File Processing

const options = {
  method: 'POST',
  headers: {
    'x-api-key': '<x-api-key>',
    'x-organization-id': '<x-organization-id>',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({event_type: '<string>', detail: {}, 'detail.file_id': '<string>'})
};

fetch('https://api.dcycle.io/v1/files/send-event', options)
  .then(res => res.json())
  .then(res => console.log(res))
  .catch(err => console.error(err));

import requests

url = "https://api.dcycle.io/v1/files/send-event"

payload = {
    "event_type": "<string>",
    "detail": {},
    "detail.file_id": "<string>"
}
headers = {
    "x-api-key": "<x-api-key>",
    "x-organization-id": "<x-organization-id>",
    "Content-Type": "application/json"
}

response = requests.post(url, json=payload, headers=headers)

print(response.text)

curl --request POST \
  --url https://api.dcycle.io/v1/files/send-event \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --header 'x-organization-id: <x-organization-id>' \
  --data '
{
  "event_type": "<string>",
  "detail": {},
  "detail.file_id": "<string>"
}
'

Retry File Processing

Use this endpoint when a file is already uploaded, but the downstream processing step has not yet produced a file_reading. Typical cases:

retrying a stalled file
re-queueing processing after operational issues
manually nudging a file that was classified but never parsed into file_reading

This is a retry hook, not the primary upload flow. The normal path is still:

upload file
confirm upload
automatic classification
automatic processing into file_reading

Request

Headers

string

required

Your API key for authenticationExample: sk_live_1234567890abcdef

string

required

Your organization UUIDExample: a8315ef3-dd50-43f8-b7ce-d839e68d51fa

Body

string

required

Use PROCESS_DOCUMENT.

object

required

Additional event detail payload.

string

required

File UUID to process.

Response

Returns true (HTTP 200) when the processing event has been accepted and queued. The actual document processing runs asynchronously.

Example

curl -X POST "https://api.dcycle.io/v1/files/send-event" \
  -H "x-api-key: ${DCYCLE_API_KEY}" \
  -H "x-organization-id: ${DCYCLE_ORG_ID}" \
  -H "Content-Type: application/json" \
  -d '{
    "event_type": "PROCESS_DOCUMENT",
    "detail": {
      "file_id": "11111111-1111-1111-1111-111111111111"
    }
  }'

import os
import requests

response = requests.post(
    "https://api.dcycle.io/v1/files/send-event",
    headers={
        "x-api-key": os.environ["DCYCLE_API_KEY"],
        "x-organization-id": os.environ["DCYCLE_ORG_ID"],
        "Content-Type": "application/json",
    },
    json={
        "event_type": "PROCESS_DOCUMENT",
        "detail": {
            "file_id": "11111111-1111-1111-1111-111111111111",
        },
    },
    timeout=30,
)

print(response.json())

const axios = require('axios');

axios.post('https://api.dcycle.io/v1/files/send-event', {
  event_type: 'PROCESS_DOCUMENT',
  detail: {
    file_id: '11111111-1111-1111-1111-111111111111',
  },
}, {
  headers: {
    'x-api-key': process.env.DCYCLE_API_KEY,
    'x-organization-id': process.env.DCYCLE_ORG_ID,
    'Content-Type': 'application/json',
  },
}).then(response => console.log(response.data));

Successful Response

true

true means the processing event was accepted and queued.

What Happens Next

After the event is accepted:

the processing pipeline runs asynchronously
a file_reading may be created or updated
clients can poll GET /v1/files/readings?file_id=<file-id>

Common Errors

401 Unauthorized

Cause: Missing or invalid API key

{"detail": "Invalid API key for organization", "code": "INVALID_API_KEY"}

403 Forbidden

Cause: The authenticated user is not a member of the organization

{"detail": "Logged User is not Member of Organization", "code": "LOGGED_USER_NOT_MEMBER"}

422 Unprocessable Entity

Cause: Missing required fields (event_type, detail.file_id)

{
  "detail": [
    {
      "loc": ["body", "event_type"],
      "msg": "field required",
      "type": "value_error.missing"
    }
  ]
}

Notes

This endpoint does not return the file_reading directly.
It only queues the processing event.
If the file has not been classified yet, you may need classification first before processing succeeds.
This endpoint can be safely treated as a retry operation for operational recovery.

Upload Files

Upload files via presigned S3 URLs

List File Readings

Check processing results

Update Reading

Edit extracted content

Create Records

Convert readings into invoices or wastes

Upload Files List File Readings

​Retry File Processing

​Request

​Headers

​Body

​Response

​Example

​Successful Response

​What Happens Next

​Common Errors

​401 Unauthorized

​403 Forbidden

​422 Unprocessable Entity

​Notes

​Related Endpoints

Upload Files

List File Readings

Update Reading

Create Records

Retry File Processing

Request

Headers

Body

Response

Example

Successful Response

What Happens Next

Common Errors

401 Unauthorized

403 Forbidden

422 Unprocessable Entity

Notes

Related Endpoints