Pular para conteúdo principal
Nenhum item encontrado.
Logo do DropboxSign
Por que usar o Dropbox Sign?
Expandir ou recolher o acordeão

O que você é possível fazer

Assinar documentos on‑line
Crie assinaturas eletrônicas
Escolha ou crie modelos
Preencher e assinar PDFs
Concluir contratos on-line
Gerenciamento de documentos
Explorar recursos
Ícone de flecha para direita

Casos de uso

Vendas e desenvolvimento de negócios
Recursos humanos
Startups
Tecnologia financeira
Imobiliária
Serviços sob demanda
Produtos
Expandir ou recolher o acordeão
ícone do Dropbox
Sign
Facilite o envio e a assinatura
ícone do Dropbox
Sign API
Integre a eSign em seus fluxos de trabalho
Ícone de Dropbox Fax
Fax
Envie faxes sem usar um aparelho de fax
Ícone de Integrações do Dropbox
Integrações
Nós vamos até você
Recursos
Expandir ou recolher o acordeão
Blog
Experiência em fluxo de trabalho e novidades sobre produtos
Histórias de clientes
Histórias do mundo real com resultados reais
Central de ajuda
Orientação detalhada para nossos produtos
Biblioteca de recursos
Relatórios, vídeos e folhetos de informações
Desenvolvedores
Preços
Expandir ou recolher o acordeão
Preços do Dropbox Sign
Encontre o plano mais adequado para você
Preços da Dropbox Sign API
Histórias do mundo real com resultados reais
Fale com vendas
Registrar‑se
Fale com vendas
Acessar conta
Expandir ou recolher o acordeão
Dropbox Sign
Dropbox Forms
Dropbox Fax
Conta de avaliação gratuita
Blog
/
Desenvolvedores

Rate limits and best practices to avoiding them

by 
Ana Orozco
July 9, 2020
4
minutos de leitura
"Rate limits and best practices to avoiding them" header image
ícone de dica de ferramenta

Novo visual, mesmo produto incrível! O HelloSign agora é Dropbox Sign.

ícone fechar

You go out for dinner and, coincidentally, 50 other people decided to go to the same restaurant at about the same time, so you get to the waitlist. Do you know why we need to form a line to get a table at the restaurant? That’s right! It’s because there’s a “maximum occupancy” the restaurant can hold (I’m sure you’ve seen these little signs). The occupancy limits exist in all public venues to ensure public safety.

‍

Similarly, the Dropbox Sign API uses a system called "rate limits" to ensure the stability of the API to service the client request.

‍

Each time the Dropbox Sign API is hit, regardless of the verb used, it counts as an API request. If your application makes a lot of API requests in a short amount of time, you may bump into the API rate limit. You will know this has happened when you get an error message like the following:

Or an email like this:

When you reach the limit, the Dropbox Sign API stops processing any more requests until the required amount of time has passed. The rate limits for a DropboxSign account are outlined in the Rate limits section of the API documentation.

‍

This article is intended to define best practices for avoiding rate limiting in the Dropbox Sign API.

Reducing the number of API requests

First and foremost, make sure your application is making only the requests that it needs. Here are some ideas to explore to optimize your code to eliminate any unnecessary API calls:

  1. Avoid polling the API, use Callbacks instead. An example of this is when retrieving the final document after a signature request has been completed: once the document has been signed, it still needs to be processed; how long this processing takes varies. If you call for the document too soon, you’ll get a “document is still processing” response and you will need to wait and try again later. This “try again later” means additional API calls that will consume your rate limits. Instead, you’ll want to listen for the "signature_request_all_signed" callback event, which is triggered only once the final file is processed and ready to be downloaded, and tie the document download to it. This way you will be making only one API call that will work for sure.
  2. Cache your own data when you need to store specialized values or rapidly review very large data sets. You can also save static information in a database or even serialize it in a file. For example, if your site allows users to browse your template library, you’ll want to have your templates stored in a database and pull the template list from there instead of making an API call every time the user needs to choose a template. This would not only reduce the risk of hitting a rate limit in the way but also improve performance, not to mention reducing the dependency to the API itself. In an implementation like this, you'd only need to call the API to update your database with new templates - or even better, listen to the "template_created" callback event and have your app do it automatically without even needing to call the API-.
  3. Ask yourself, are there requests getting data items that aren't used in my application? What am I using that “signature request list” call I’m making every time a user gets to this page for?
  4. Use bulk endpoints such as Bulk Send with Template, which lets you sends up to 250 signature requests in bulk with a single API request, instead of making 250 “Send with Template” calls.
  5. If you need to backfill data, consider doing it in batches. For example, currently the best approach to download your document library is to use the API. A good way to do it is setting it up as a script and run the script in batches with wait times that will respect the rate limit.

Monitoring API activity

You can use the API dashboard in the DropboxSign portal to monitor your API activity against your limits:

A screenshot of the Dropbox Sign API requests dashboard, showing API request usage

‍

You can also consider including a process in your code that regulates the rate of your requests so that they're distributed more evenly over time. For this you could, for example, use the following API response headers to confirm your account's current rate limit and monitor the number of requests remaining in the current period:

These headers are included by default in every response our API sends to your application.

Catching errors caused by rate limits

Ideally, your application handles the rate limit exception gracefully instead of crashing (ideally, right?).

‍

As a best practice, make sure to notify the user of the situation. Depending on the workflow that’s being executed, you’ll want to let them know that the application isn’t broken and that there’s hope: they’ll be able to retry the operation. Usual example messages are similar to:

‍

Questions? Reach out!

Fique por dentro

Pronto! Verifique sua caixa 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
Ícone de flecha para direita
ícone fechar

Up next:

Ilustração em close-up de uma assinatura manuscrita, representando soluções modernas de assinatura digital.
Desenvolvedores
15
minutos de leitura

Como integrar o Dropbox Sign ao Ruby on Rails: um tutorial passo a passo

Ilustração em close-up de uma assinatura manuscrita, representando soluções modernas de assinatura digital.
Desenvolvedores
15
minutos de leitura

Dropbox Sign vs. SignNow for developers

eBook

O kit de ferramentas de automação de RH: ferramentas essenciais para um acervo de RH bem alinhado

Produtos
Dropbox SignDropbox Sign APIDropbox FaxIntegrações
Por que o Dropbox Sign?
Assinaturas eletrônicasAssinar documentosAssinar e preencher PDFsContratos on-lineCrie assinaturas eletrônicasEditor de assinaturasAssine documentos do Word
Atendimento
Central de ajudaFale com vendasEntrar em contato com o atendimentoGerenciar cookiesIntrodução: Dropbox SignIntrodução: Dropbox Sign API
Recursos
BlogHistórias de clientesCentral de recursosGuia de legalidadeCentral de confiança
Parceiros
Parceiros estratégicosLocalizador de parceiros
Empresa
CarreirasTermosPrivacidade
ícone do Facebookícone do Youtube

Métodos de pagamento aceitos

Logo da MastercardLogo do VisaLogo da American ExpressLogo do Discover
Emblema de conformidade CPAEmblema de Conformidade com HIPAAEmblema da Sky High Enterprise ReadyEmblema do Certificado ISO 9001

As assinaturas eletrônicas do Dropbox Sign são juridicamente vinculativas nos Estados Unidos, União Europeia, Reino Unido e muitos outros países do mundo.
Para mais informações, consulte nossosTermos e Condições e nossa Política de Privacidade