What processing_lane does
Optional processing_lane controls the start SLA (queue start, not completion) and the credit price.
processing_lane decides when the job starts in the queue. client_wait decides whether the HTTP connection waits for the result. The two fields are independent.
Lanes
| Lane | Typical time to job start | Credit factor |
|---|---|---|
no_sla | Best effort | ×1 |
sla_24h | Start within 24 hours | ×1.5 |
sla_12h | Start within 12 hours | ×2 |
sla_6h | Start within 6 hours | ×3 |
sla_1h | Start within 1 hour | ×4 |
instant | Immediate start | ×5 |
Default — no surcharge
Without processing_lane the workspace default (default_processing_lane) applies, otherwise no_sla (factor 1.0).
Every plan includes Best Effort. Faster lanes are optional surcharges.
Request
POST /job/add/paperoffice_aiocr___generate
Authorization: Bearer po_sk_...
Content-Type: application/json
{
"file": "<base64 or URL>",
"processing_lane": "sla_1h",
"client_wait": true,
"max_wait_seconds": 60
}Aliases: start_sla and sla_lane. Legacy priority remains internal; processing_lane wins. Live factors: GET /job/pricelist.
In integrations set processing_lane when a start SLA is required, or omit it for Best Effort (multiplier 1.0).