August 19, 2026Cryvis

Connect the Cryvis REST API in Make.com

End-to-end Make.com pattern for Cryvis REST: Bearer auth, multipart upload, parse JSON, map fields, and error handling on real document endpoints.

Cryvis is a plain REST API: HTTPS, Bearer token, multipart uploads, JSON responses. Make does not need a native Cryvis app—HTTP — Make a Request plus a file source is the entire connection pattern.

This post is the spine that the other HTTP tutorials specialize. Hub: Make.com + Cryvis. API overview: Documentation.

Architecture

[Source app]          [Cryvis]                 [Destination]
Watch / Webhook  →  HTTP POST multipart  →  Sheets / CRM / Slack
Download binary     Bearer auth
                    Parse JSON

There is no generic PDF OCR path. Choose:

POST https://api.cryvis.com/v1/documents/<type>
POST https://api.cryvis.com/v1/custom-extractors/<slug>

Decision guide: Extract PDF data. Custom product: Custom API. Built-ins: Invoice, Receipt, Passport, and the other /apis/* pages.

Step-by-step connection

1. API key

Create a key in Console → API keys. Store it for Make as described in Add Bearer authentication.

2. Source binary

Drive Download, Gmail attachment download, Dropbox get file—anything that yields a Buffer. Upload file to API.

3. HTTP module

Setting	Value
URL	Real Cryvis endpoint (see cheat sheet)
Method	POST
Headers	`Authorization: Bearer …`
Body type	Multipart/form-data
Fields	Per endpoint (multipart guide)
Parse response	Yes

4. Map JSON

Single-doc: data.* + meta.request_id. Batch: iterate results[]. Parse responses, Map fields.

5. Error Handler

Break + alert on 401/402/422/502. Router for soft meta.validation.warnings. Handle API errors.

Endpoint cheat sheet

https://api.cryvis.com/v1/documents/invoice
https://api.cryvis.com/v1/documents/receipt
https://api.cryvis.com/v1/documents/passport          # first_page, last_page
https://api.cryvis.com/v1/documents/pan
https://api.cryvis.com/v1/documents/aadhaar
https://api.cryvis.com/v1/documents/driver-license    # file + country
https://api.cryvis.com/v1/documents/indian-vehicle-rc # front, back
https://api.cryvis.com/v1/custom-extractors/<slug>    # file

MIME: PDF, JPEG, PNG, WebP. Credits: 1 per page / image (credits).

Minimal working example (invoice)

Drive Watch → Drive Download → HTTP invoice → Sheets Add Row

Concrete clicks: Send PDF to OCR API (invoice URL—not a fictional /ocr).

Minimal custom example

Console schema → slug
Gmail PDF → HTTP /v1/custom-extractors/<slug> → Airtable

Build custom extractor, Convert PDFs to JSON.

Connection reuse

Keep one Cryvis auth configuration (variable or HTTP connection) shared across scenarios. Clone modules when adding document types; only URL, multipart fields, and mappings change.

Optional: Schedule vs instant Watch—same HTTP core. Pattern catalog: Extract structured data from documents.

Verification checklist

curl with the same key and a sample file succeeds
Make HTTP returns success: true in the output bubble
Destination row shows real data values (not empty)
Intentional bad key produces 401 handled by Error Handler
Credits visible moving in Console after a page upload

What “connected” means

You are connected when Make can authenticate, upload bytes with correct multipart names, parse the Cryvis envelope, and write destinations—with failures observable. That is the whole REST integration surface; everything else is document-type specifics linked from the Make.com hub.