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

Jotform User API

The User API from Jotform — 13 operation(s) for user.

Jotform User API is one of 10 APIs that Jotform publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.

Tagged areas include User. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, and an AsyncAPI specification.

This API exposes 14 operations across 13 paths. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against 3 base URLs: https://api.jotform.com, https://eu-api.jotform.com, https://hipaa-api.jotform.com.

14 operations 13 paths 0 schemas 11 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.jotform.com
Authentication
API Key, API Key
Resource Areas
1

Authentication & Security 2

Jotform User API declares 2 security schemes for authenticating requests. An API key is passed in the header as APIKEY (ApiKeyHeader). An API key is passed in the query as apiKey (ApiKeyQuery). By default, every request must be authenticated.

Paths & Operations 14

Across 13 paths, the API surfaces 14 operations — 11 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

User 14
GET
/user
Get user details
getUser → 200
GET
/user/usage
Get monthly user API usage and limits
getUserUsage → 200
GET
/user/settings
Get user account settings
getUserSettings → 200
POST
/user/settings
Update user account settings
updateUserSettings body → 200
GET
/user/settings/{settingsKey}
Get a single user settings value by key
getUserSettingByKey 1 param → 200
GET
/user/history
Get user activity log
getUserHistory → 200
GET
/user/submissions
List all submissions across all forms owned by the user
getUserSubmissions → 200
GET
/user/subusers
List sub-users of the account
getUserSubusers → 200
GET
/user/reports
List reports across all forms owned by the user
getUserReports → 200
GET
/user/forms
List forms owned by the user
getUserForms → 200
GET
/user/folders
List the user's folder tree
getUserFolders → 200
POST
/user/register
Register a new Jotform user account
registerUser body → 200
POST
/user/login
Log a user in and obtain an app key
loginUser body → 200
GET
/v1/user/logout
Log the current user out and invalidate the app key
logoutUser → 200

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

jotform-user-api-openapi.yml Raw ↑

Other APIs Jotform publishes across the network.

Jotform REST API (EU)
Jotform REST API (HIPAA)
Jotform Folder API
Jotform Form API
Jotform Label API
Jotform Report API
Jotform Submission API
Jotform System API
Jotform Webhook API
Where this information came from

This is an independent, third-party profile of Jotform User 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.