Help Center menu

Public API status

In this article

There's no public REST API today. This article covers what's planned and what your options are in the meantime.

What's planned

A public REST API is on the roadmap. Planned endpoints include:

  • GET /forms — list your forms
  • GET /forms/:id — fetch a form's schema (blocks, settings, styling)
  • GET /forms/:id/responses — paginated list of responses
  • GET /responses/:id — fetch a single response
  • POST /forms/:id/webhooks — manage webhook subscriptions
  • DELETE /responses/:id — remove a response

No firm ETA yet — sign up for early access by emailing support@nodumforms.com with your use case.

What you can do today

  • Webhooks for outbound (write) integrations — every submission fires a POST to your URL.
  • CSV export for read-only one-shot exports — manual but reliable for periodic data pulls.
  • Zapier / Make for no-code workflows that respond to new submissions.

Why no API yet?

Building a public API is a forever commitment — once shipped, breaking changes are painful for every consumer. We're using the beta period to nail down the response schema, auth model, and rate limits before locking them in. If you have specific API needs we should account for, we want to hear about them at support@nodumforms.com.

Give feedback

Was this resource helpful?

|

Up next

Using CSV export programmatically

Until the REST API ships, CSV export is the best way to get response data out of NodumForms for downstream use.

Read more
Previous: Integrating with webhooks

FAQs

Not yet — a public REST API is on the roadmap. Today the only outbound integration point is the webhook on each form, which fires on every submission with the full response payload. If you need read access to forms or responses programmatically before the API ships, email support@nodumforms.com.

No SDK yet — the planned TypeScript / Python / Go libraries are blocked on shipping the public REST API. Watch the roadmap for announcements.

Webhook signing isn't available yet — the request has no signature header. As a workaround, protect the endpoint by using a hard-to-guess URL path. Signing is on the roadmap.