Pasar al contenido principal
No se ha encontrado ningún elemento.
Logotipo de Dropbox Sign
¿Por qué elegir Dropbox Sign?
Desplegar o contraer acordeón

Qué puedes hacer

Firmar documentos en línea
Crea firmas electrónicas
Selecciona o crea plantillas
Rellenar y firmar PDF
Finalizar contratos en línea
Gestión de documentos‍
Ver funciones
Icono de flecha hacia la derecha

Casos prácticos

Desarrollo comercial y de negocio
Recursos humanos
Start-ups
Tecnología financiera
Propiedad inmobiliaria
Servicios a la carta
Productos
Desplegar o contraer acordeón
Icono de Dropbox
Sign
Facilita el envío y la firma
Icono de Dropbox
Sign API
Integra las firmas electrónicas en tu flujo de trabajo
Icono de Dropbox Fax
Fax
Envía faxes sin tener fax
Icono de integraciones de Dropbox
Integraciones
Estamos donde trabajas
Recursos
Desplegar o contraer acordeón
Blog
Amplios conocimientos sobre flujos de trabajo y noticias sobre productos
Experiencias de clientes
Historias reales con resultados tangibles
Centro de ayuda
Consejos avanzados para usar nuestros productos
Colección de recursos
Informes, vídeos y hojas informativas
Desarrolladores
Precios
Desplegar o contraer acordeón
Precios de Dropbox Sign
Encuentra el plan perfecto para ti
Precios de Dropbox Sign API
Historias reales con resultados tangibles
Contactar con ventas
Registrarse
Contactar con ventas
Iniciar sesión
Desplegar o contraer acordeón
Dropbox Sign
Dropbox Forms
Dropbox Fax
Pruébalo gratis
Blog
/
Desarrolladores

Using Dropbox Sign API Callbacks

por 
Ana Orozco
December 13, 2019
3
minutos de lectura
"Using Dropbox Sign API Callbacks" header image
icono de mensaje emergente

Cambio de imagen, pero ¡el mismo gran producto! HelloSign ahora es Dropbox Sign.

icono de cerrar

Let’s start by defining callbacks (otherwise known as webhooks). There are two ways two apps can communicate with each other to share information: polling and callbacks. Polling is like going on a roadtrip and asking the driver “are we there yet?” every 5 minutes. Callbacks are like falling asleep and having the driver wake you up once you are finally there.

‍

Callbacks are automated messages sent from apps to notify that something happened. They have a payload (or body) and are sent to a unique URL.

‍

The Dropbox Sign API sends callbacks for the life cycle of a signature request. Instead of calling the API to check the status of a request, you can listen for these callbacks to build a reliable flow in your application.

‍

Let’s take the example of creating a simple signature request. After you call the “signature_request/create_embedded” endpoint, you receive a response from the API with a status (“200” if it was successful. Otherwise, learn our error messages) and a JSON containing information pertinent to the call you made. This response is useful because it gives you basic information about the request, lets you know that our server received it successfully and there were no issues with the parameters you passed in.

‍

Here is what is happening behind the scenes:

A diagram showing a callback with Dropbox Sign API

‍

If, for example, there was an issue during document processing because the uploaded document has a text tag that is malformed, this is flagged as an error and our API will want to notify you that this happened through a callback event. Wouldn’t it be nice for you to know there was an issue with your file right away instead of having to figure it out the hard way?

‍

This is why it is a best practice to wait for the “signature_request_sent” callback (which only fires once document processing is complete) before attempting to open a sign url in the iFrame. In the case of the error we used as an example, a “file_error” callback will be sent instead. This is how an example of the “file_error” callback event will look like in the API Dashboard:

Screenshot of the "file_error" callback event in the Dropbox Sign API dashboard
Note: to see something like the above, you need to make sure to be logged in with the  Dropbox Sign account that owns the app the requests are being made with.

‍

Another example of when you can benefit from callbacks is downloading the final (signed) document. The “signature_request_all_signed” callback will trigger only after all the signers have completed the document and it’s ready for download. In this case, a best practice is to wait for the “signature_request_all_signed” callback event and then trigger the document download. This ensures that you will get the final copy of the document with all signatures and the “completed” status on the audit trail.

Responding to callbacks

The Dropbox Sign API will send callbacks to whatever URL you tell it to. You can set your account callback by using the account API call or manually on the settings page.

‍

Your endpoint will need to return a 200 HTTP code and a response body containing the following text: “Hello API Event Received.” Otherwise, the callback will be considered a failure and will be retried later. Refer to the “Events and Callbacks” article for more information on this. To illustrate the workflow:

‍

Diagram showing how to respond to callbacks using the Dropbox Sign API

‍

Other resources on this topic:

Example Dropbox Sign API Callback Event

The difference between signature_request_signed and all_signed callback events.

Example Java Callback Handler

Simple PHP Callback Handler

A Simple Python Callback Handler

Example of how to use ngrok (or other localhost tunneling software) to test callback handlers

Tools for Testing the API and Callbacks Locally

No pierdas el hilo

¡Listo! Revisa tu bandeja de entrada.

Thank you!
Thank you for subscribing!

Lorem ipsum

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum
Icono de flecha hacia la derecha
icono de cerrar

Up next:

Ilustración en primer plano de una firma manuscrita, que representa soluciones modernas para la firma digital.
Desarrolladores
15
minutos de lectura

Integración de Dropbox Sign con Ruby on Rails: un tutorial paso a paso

Ilustración en primer plano de una firma manuscrita, que representa soluciones modernas para la firma digital.
Desarrolladores
15
minutos de lectura

Dropbox Sign vs. SignNow for developers

Infografía

Cuatro formas en las que las API de firma electrónica pueden optimizar tus procesos empresariales

Productos
Dropbox SignDropbox Sign APIDropbox FaxIntegraciones
Por qué Dropbox Sign
Firmas electrónicasFirmar documentosFirma y rellena documentos PDFContratos onlineCrea firmas electrónicasEditor de firmasFirma de documentos de Word
Asistencia
Centro de ayudaContactar con ventasPonte en contacto con el departamento de asistencia.Gestionar cookiesPrimeros pasos: Dropbox SignPrimeros pasos: Dropbox Sign API
Recursos
BlogExperiencias de clientesCentro de recursosGuía de legalidadCentro de confianza
Socios
Socios estratégicosLocalizador de socios
Empresa
EmpleoCondicionesPrivacidad
Icono de FacebookIcono de YouTube

Métodos de pago aceptados

Logotipo de MastercardLogotipo de VisaLogotipo de American ExpressLogotipo de Discover
Insignia de conformidad con la CPAInsignia de conformidad con la HIPAAInsignia de Sky High Enterprise-ReadyInsignia de certificación ISO 9001

Las firmas electrónicas de Dropbox Sign son legalmente vinculantes en los Estados Unidos, la Unión Europea, el Reino Unido y en muchos otros países.
Para obtener más información, consulta nuestros Términos y condiciones y la Política de privacidad.