Two companies. One venture. A partnership neither could pull off alone. World Industries and Meridian Corp have found the kind of deal that comes around once — combining strengths, splitting nothing, both sides better off than they started. No losers here. Just two boards who see what's possible together, and a deadline before the opportunity moves on.
The only thing standing between a handshake and a headline is trust — proof that every signature is real, every document is untampered, and every step is recorded beyond dispute. That's where you come in.
To launch the venture safely, you'll need to command the three forces of the signing workflow:
Every field must be signed. Every step must be verifiable. Two companies are betting their future on this moment — and on a platform they can trust. Make it count.
Objective: Build a signing workflow end-to-end — upload a document, create an envelope with two recipients in sequential signing order, send it, and confirm completion.
This mission sends real signing notifications to two email addresses. Before running the steps, open the Doctavian collection in Postman, go to Variables, and set the following:
| Variable | Description |
|---|---|
mission2.partyAEmail | We recommend using your own email here — as Party A you'll sign the envelope, as sender you'll get status notifications, and you'll also be able to view the envelope through the portal |
mission2.partyAName | Full name of Party A |
mission2.partyBEmail | Email address of Party B — notified after Party A signs |
mission2.partyBName | Full name of Party B |
Use email addresses you have access to — both parties will receive signing notifications and will need to complete the signing session for the mission to reach
Completedstatus.
Before running the steps, Download the Joint Venture Agreement and take a look at where the two Signature lines sit — one for Party A, one for Party B. Knowing their position on the page makes it much easier to follow how the fields are placed in Step 2.
Open the Doctavian Postman collection and navigate to the Mission 2 — The Meridian Merger folder. Run the steps in order — each one builds on the previous.
Don't have the collection yet? Make sure you've completed the Quickstart and have a valid access token before starting.
Unlike Document Generation, the Signatures API doesn't separate the pieces into independent resources you assemble one at a time. The entire envelope — every document, every recipient, every signature field, every rule — is built and sent in a single, tightly structured request. This mission walks through what's actually inside that request and why each piece matters.
Before the envelope can be assembled, the document must be in Doctavian storage. Open Step 1 — Upload the joint venture document in Postman, attach the file you downloaded earlier, and send the request.
The response returns a URN that uniquely identifies this file in storage. That URN is the only thing the envelope create request needs to know about the document — Doctavian doesn't need the file re-uploaded with every API call, just a reference to where it already lives. The collection saves the returned URN as {{uploadedDocument}} — you'll need it in the next step.
A 200 OK with a URN in the response confirms the document is uploaded and ready.
Open Step 2 — Create the envelope. This single request body has four distinct sections, each playing a different role:
{{uploadedDocument}} and assigns it referenceDocumentId: 1. This local ID is what the fields section below uses to point back at this specific document — it has nothing to do with the document's real URN, it only needs to be unique within this request.referenceSignerId (1 and 2). Both are marked mandatory: true, meaning if either one declines, the whole envelope is voided — there's no partial deal here.referenceDocumentId and referenceSignerId. The positions correspond to the Signature lines printed on the agreement itself:
referenceDocumentId: 1, referenceSignerId: 1, positioned at approximately X: 75, Y: 720referenceDocumentId: 1, referenceSignerId: 2, positioned at approximately X: 420, Y: 720isSignOrder: true enforces sequential signing in the order recipients were listed, expireInDays: 5 sets the deadline, and the reminder settings control how persistently Doctavian chases a signature before that deadline hits.The isSignOrder flag is what actually creates the sequencing here. With it set to true, Party B receives no notification at all until Party A has completed every field assigned to them — the two recipients never have simultaneous access to the document.
Send the request. The collection saves the returned envelopeId as {{envelopeId}} automatically. A 201 Created confirms the envelope is assembled and in Draft state.
The envelope is in
Draftuntil you send it — no notifications go out yet. You can inspect and edit it at this point. You can also open the envelope directly in the Doctavian Portal to see it exactly as a portal user would.
Open Step 3 — Send the envelope and send the request. This is the moment the envelope stops being a configuration and becomes a live transaction. Because of isSignOrder: true, only Party A receives a notification email right now — Party B's turn hasn't started yet, and won't until Party A's signature field is completed.
A 200 OK confirms the envelope is sent and the status has moved to Sent.
This mission signs through the Doctavian portal, not the API — programmatic signing involves an extra legal consent steps which we'll save for a deeper dive later.
Party A and Party B will each receive a personalised email inviting them to sign through the portal, and you — as the sender — will receive updates as the envelope is opened and signed. Step 4 below shows you how to track that progress via the API.
Open Step 4 — Check envelope status and send the request. The response shows the envelope's overall status alongside the individual signing status of each recipient — this is how you'd track progress programmatically rather than waiting on email notifications alone.
Once Party A signs, two things happen behind the scenes: the envelope's audit trail logs the completion, and Doctavian automatically dispatches the notification to Party B — no separate API call required to advance the sequence. Run this step again after both parties have signed to confirm the full sequence completed.
A completed envelope returns status: "Completed" with both recipients showing status: "Completed".
isSignOrder and the order recipients are listedThe agreement is signed. The joint venture starts. Continue to Mission 3 — The Empire Scales →