How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Nitro Software Sign API

The Sign API from Nitro Software — 22 operation(s) for sign.

Nitro Software Sign API is one of 3 APIs that Nitro Software publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Sign. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 32 operations across 22 paths, and defines 72 schemas. It is described by OpenAPI 3.2.0, at version 0.1.

Requests are made against a single base URL, https://api.gonitro.dev.

32 operations 22 paths 72 schemas 4 DELETE13 GET4 PATCH9 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.1
Base URL
https://api.gonitro.dev
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Nitro Software Sign API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth). By default, every request must be authenticated.

Paths & Operations 32

Across 22 paths, the API surfaces 32 operations — 4 DELETE, 13 GET, 4 PATCH, 9 POST, 2 PUT. Each is listed below with its method, path, parameters, and response codes.

Sign 32
PUT
/sign/envelopes/{envelopeID}:cancel
Cancel Envelope by ID
cancelEnvelope 1 param → 200404409401
PUT
/sign/envelopes/{envelopeID}/documents:reorder
Reorder Documents by Envelope ID
reorderDocuments 1 param body → 200404409401
POST
/sign/envelopes/{envelopeID}:send-reminders
Send Reminders for Envelope
sendReminders 1 param body → 202404409401
POST
/sign/envelopes/{envelopeID}:send-for-signing
Send Envelope for Signing
sendForSigning 1 param → 200404409401
POST
/sign/envelopes/{envelopeID}/participants:batch-delete
Delete Participants by Participant IDs
deleteParticipants 1 param body → 200404401
GET
/sign/envelopes/{envelopeID}/participants
List Participants by Envelope ID
listParticipants 1 param → 200404401
POST
/sign/envelopes/{envelopeID}/participants
Create Participant(s) by Envelope ID
createParticipant 1 param body → 201200400404401
POST
/sign/envelopes/{envelopeID}/documents/{documentID}/fields:batch-delete
Delete Fields by Field IDs
deleteFields 2 params body → 200404401
GET
/sign/envelopes/{envelopeID}/documents/{documentID}/fields
List Fields by Document ID
listFields 2 params → 200404401
POST
/sign/envelopes/{envelopeID}/documents/{documentID}/fields
Create Field(s) by Document ID
createField 2 params body → 201200400404422401
GET
/sign/envelopes/{envelopeID}/documents
List Documents by Envelope ID
listDocuments 1 param → 200404401
POST
/sign/envelopes/{envelopeID}/documents
Create Document by Envelope ID
createDocument 2 params body → 201400413415422401
GET
/sign/envelopes
List Envelopes
listEnvelopes 2 params → 200401
POST
/sign/envelopes
Create Envelope
createEnvelope body → 201400401
POST
/sign/conversionsdeprecated
Convert File to PDF
convertFile body → 200400415413500401
DELETE
/sign/envelopes/{envelopeID}/participants/{participantID}
Delete Participant by ID
deleteParticipant 2 params → 204404401
PATCH
/sign/envelopes/{envelopeID}/participants/{participantID}
Update Participant by ID
updateParticipant 2 params body → 200400404401
DELETE
/sign/envelopes/{envelopeID}/documents/{documentID}/fields/{fieldID}
Delete Field by ID
deleteField 3 params → 204404401
PATCH
/sign/envelopes/{envelopeID}/documents/{documentID}/fields/{fieldID}
Update Field by ID
updateField 3 params body → 200404401
GET
/sign/envelopes/{envelopeID}/documents/{documentID}
Get Document by ID
getDocument 2 params → 200404401
DELETE
/sign/envelopes/{envelopeID}/documents/{documentID}
Delete Document by ID
deleteDocument 2 params → 204404409401
PATCH
/sign/envelopes/{envelopeID}/documents/{documentID}
Update Document by ID
updateDocument 2 params body → 200400404409401
GET
/sign/envelopes/{envelopeID}
Get Envelope by ID
getEnvelope 1 param → 200404401
DELETE
/sign/envelopes/{envelopeID}
Delete Envelope by ID
deleteEnvelope 1 param → 204400401
PATCH
/sign/envelopes/{envelopeID}
Update Envelope
updateEnvelope 1 param body → 200400404409401
GET
/sign/envelopes/{envelopeID}:download-sealed
Download Sealed Envelope
downloadSealedEnvelope 1 param → 200404409401
GET
/sign/envelopes/{envelopeID}:download-original
Download Original Envelope
downloadOriginalEnvelope 1 param → 200404401
GET
/sign/envelopes/{envelopeID}:download-audit-trail
Download Audit Trail of Envelope
downloadAuditTrailOfEnvelope 1 param → 200404401
GET
/sign/envelopes/{envelopeID}/participants/signing-urls
List Signer Signing URLs by Envelope ID
listSignerSigningUrls 1 param → 200404409401
GET
/sign/envelopes/{envelopeID}/documents/{documentID}:download-sealed
Download Sealed Document by ID
downloadSealedDocument 2 params → 200404409401
GET
/sign/conversions/{jobID}:download-converteddeprecated
Get Converted File by Job ID
downloadConvertedFile 1 param → 200404500401
GET
/sign/conversions/{jobID}/statusdeprecated
Get Conversion Job Status
getJobStatus 1 param → 200404500401

Schemas 72

The contract defines 72 schemas that model the data the API accepts and returns. The most detailed are Date (9 properties), CreateDateFieldResponse (9 properties), Custom (8 properties), CreateCustomFieldResponse (8 properties). Each schema is shown below with its type and property counts.

Envelope
object
5 properties
ParticipantList
object
Fields
2 properties
BadRequestProblemDetail
object
Bad Request error details
6 properties
SendReminders
object
1 property
Date
object
Response representing a Date field
9 properties 5 required
CreateNameField
object
Parameters to create a Name field
5 properties 3 required
UpdateInitialsField
object
Parameters to update a Initials field
5 properties 1 required
UpdateCompanyField
object
Parameters to update a Company field
5 properties 1 required
DeleteFieldsRequest
object
A set of unique UUIDv4 strings that identify the fields in the Nitro system.
1 property
Title
object
Response representing a Title field
7 properties 4 required
Custom
object
Response representing a Custom field
8 properties 5 required
ContentTooLargeProblemDetail
object
Content too large error details
6 properties
UpdateNameField
object
Parameters to update a Name field
5 properties 1 required
CreateCustomField
object
Parameters to create a Custom field
6 properties 3 required
InternalServerErrorProblemDetail
object
Internal Server Error details
6 properties
EnvelopeList
object
Fields
2 properties
CreateInitialsField
object
Parameters to create a Initials field
5 properties 3 required
EnvelopeUpdate
object
3 properties
ConvertFileResponse
object
3 properties 1 required
CreateDateField
object
Parameters to create a Date field
7 properties 3 required
SealedDocumentResponse
object
Response for a sealed document
6 properties 2 required
Company
object
Response representing a Company field
7 properties 4 required
SMS
object
SMS
3 properties
PendingDocumentResponse
object
Response for a pending document
4 properties 2 required
RenameDocumentRequest
object
1 property 1 required
CreateSignatureFieldResponse
object
Create Signature Field Response
7 properties 4 required
UpdateCustomField
object
Parameters to update a Custom field
6 properties 1 required
UnprocessableEntityProblemDetail
object
Unprocessable Entity error details
6 properties
CreateTitleFieldResponse
object
Create Title Field Response
7 properties 4 required
EnvelopeInInvalidStateProblemDetail
object
Envelope in invalid state
6 properties
JobStatusResponse
object
2 properties
DeleteParticipantsRequest
object
A set of unique UUIDv4 strings that identify the participants in the Nitro system.
1 property
Initials
object
Response representing an Initials field
7 properties 4 required
ParticipantCreate
object
Request to create a new participant
3 properties 1 required
CreateTitleField
object
Parameters to create a Title field
5 properties 3 required
UpdateDateField
object
Parameters to update a Date field
7 properties 1 required
CreateCompanyField
object
Parameters to create a Company field
5 properties 3 required
SignedDocumentResponse
object
Response for a signed document
6 properties 2 required
ParticipantUpdate
object
1 property
BulkParticipantResponse
object
Response containing multiple created participants wrapped in an items array
1 property 1 required
Signature
object
Response representing a Signature field
7 properties 4 required
ReorderDocumentsRequest
object
The request body should contain an array named 'order' with the document IDs in the desired sequence. This will update the order of documents within the envelo…
1 property
AccessCode
object
Access code
2 properties
UpdateSignatureField
object
Parameters to update a Signature field
5 properties 1 required
EnvelopeCreate
object
3 properties 3 required
UnsupportedMediaTypeDetail
object
Unsupported Media Type error details
6 properties
ExtendedEnvelope
object
7 properties
SignerSigningUrl
object
3 properties
CreateInitialsFieldResponse
object
Create Initials Field Response
7 properties 4 required
CreateCheckboxField
object
Parameters to create a Checkbox field
5 properties 3 required
Name
object
Response representing a Name field
7 properties 4 required
CreateCheckboxFieldResponse
object
Create Checkbox Field Response
7 properties 4 required
CreateSignatureField
object
Parameters to create a Signature field
5 properties 3 required
Participant
object
4 properties
CreateNameFieldResponse
object
Create Name Field Response
7 properties 4 required
UploadedDocumentResponse
object
Response for an uploaded document
6 properties 2 required
CreateDateFieldResponse
object
Create Date Field Response
9 properties 4 required
CreateCompanyFieldResponse
object
Create Company Field Response
7 properties 4 required
EnvelopeWebDocumentRequestMetadata
object
2 properties 1 required
BulkFieldRequest
object
Create multiple fields wrapped in an items array
1 property 1 required
Notification
object
2 properties 2 required
UpdateTitleField
object
Parameters to update a Title field
5 properties 1 required
Checkbox
object
Response representing a Checkbox field
7 properties 4 required
UpdateCheckboxField
object
Parameters to update a Checkbox field
5 properties 1 required
DocumentNotFoundProblemDetail
object
Document Not Found error details
6 properties
BulkParticipantRequest
object
Create multiple participants wrapped in an items array
1 property
NotFoundProblemDetail
object
Not Found error details
6 properties
CreateCustomFieldResponse
object
Create Custom Field Response
8 properties 5 required
SingleParticipantRequest
object
Create a single participant
3 properties
FailedDocumentResponse
object
Response for a failed document
7 properties 2 required
SignerSigningUrlList
object
Fields
2 properties
UnauthorizedProblemDetail
object
Unauthorized error details
6 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nitro-software-sign-api-openapi.yml Raw ↑

Other APIs Nitro Software publishes across the network.

Nitro Software Authentication API
Nitro Software Platform API
Where this information came from

This is an independent, third-party profile of Nitro Software Sign API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.