Limits

Credits

• One credit = one recipient of one notification. It is consumed when the send is confirmed, not when the draft is prepared.
• A file by download link also costs one credit for each 10 MB or part of it, per recipient. Those credits must be paid ones: trial credits pay for the notification, not for the files (see Files by download link).
• When your lawyer verification is approved, your firm receives the trial credits listed on Pricing, with their validity. The trial is given once per person, in the first of your firms that has not had a trial yet, and each firm gets only one.
• When your trial credits run out, buy a pack under Credits (/creditos); the packs and their prices are on Pricing. No assistant can buy credits.

Documents

The 6 MB is what fits in a 10 MB message, the largest our mail provider accepts, once the attachments are encoded. What fits is attached to the message. If your documents are larger:

• Send the file by download link, if the wizard offers it (see the next section).
• Compress the PDFs. A scan at 150 dpi in greyscale is much smaller than one in colour at a higher resolution; check that it is still legible.
• Split them across more than one notification of the same case, to the same recipients: for example, the providencia and the demanda in the first and the anexos in the second. Say in each message how many there are and what each one carries. Each notification uses one credit per recipient and has its own constancia.

Files by download link

A file that does not fit as an attachment, or that is not a PDF, PNG or JPEG, can be sent by download link. The message lists it with its name, its size in bytes and its SHA-256, and each recipient downloads it from their individual link. The file is not attached.

• What you need. A payment method on file under Billing, and paid credits (from a pack or a plan). If your firm has no payment method, the wizard says where to add one. The option appears in the wizard only when it is available to your firm.
• What it costs. One additional credit for each 10 MB or part of it of the notification's files by link, per recipient. A 25 MB file to two recipients costs 2 × (1 + 3) = 8 credits. The wizard shows the cost before you send, and does not let you send if your paid credits do not cover it. It is charged at send; if the send fails, the credits are returned.
• Which types. PDF, PNG, JPEG, TIFF, MP3, WAV, M4A, OGG, MP4, MOV, WEBM, MKV, DOCX, XLSX, PPTX, ODT and ZIP, up to 2 GB per file. The name must end in the extension of its type, and the content must match it. Documents with macros and password-protected archives are not accepted.
• Scan. Every file is scanned for malware before it can be sent. A large one can take several minutes. If the scan refuses it, the wizard says why and what to do.
• Retention. A file that was sent is kept for 10 years from the send and then deleted, after notice to the firm. Its SHA-256 remains on the constancia and in the notification's evidence, so anyone who kept a copy can check it is the same file. A file uploaded and not sent is deleted after 30 days; we email you 7 days before.
• On the constancia. The constancia tells attached documents from those delivered by link, and records when the server transmitted the whole file. That transmission does not prove the recipient opened it.

Rates (/v1)

Per token, per minute: 120 requests, whatever the operation. Every answer carries RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset; over the limit the answer is HTTP 429 X_RATE_LIMITED with retry-after, the seconds to wait. Some operations add a limit of their own per person: requestUpload and confirmUpload, 30 a minute each.

Rates (MCP)

Per person, per minute, across all their tokens and every server replica:

Over the limit the answer is HTTP 429 X_MCP_RATE_LIMITED with retry-after, the seconds to wait. Uploads (the PUT) do not count; requestUpload and confirmUpload do.

Deadlines

Pages

Every list pages with _first and _after: it answers the envelope { rows, nextCursor, hasMore } when asked for _first, and the next page with _after=<nextCursor> (quickstart). Without _first, it answers bare rows, as before. A value above the maximum is refused with 400 X_INPUT_INVALID: it is never cut down.

The lists that already took limit and cursor (the previous page's last row as <createdAt>_<id>) still take them; listDeadlines takes cursor as the last row's id. A new client needs only _first and _after.

exportNotifications is not a list but an Excel workbook (.xlsx, base64 in xlsx): up to 5,000 lines per call. When there are more, it answers truncated: true and a nextCursor; send it back as cursor, with the same filters, for the next file.