Skip to content
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
146 lines (110 sloc) 6.83 KB


Fastfill API Implementation Guide

This is a reference manual and configuration guide for the Fastfill API. It illustrates how to immediately retrieve information from an ID image.

Revision history

Information about changes to features and improvements documented in each release is available in our Revision history.

Table of Contents

Using the Fastfill API

Call the RESTful HTTP POST API fastfill from your server with the below parameters to create a transaction for each user. Simply submit front and/or back side image(s) of the user's document with a maximum file size of 5 MB and you will immediately receive the ID information as a JSON response.
Note: Requests originating from the client are not supported (CORS is disabled) and the API credentials must never be exposed on the client side.

HTTP request method: POST
If your customer account is in the EU data center, use instead of

Authentication: The API call is protected. To access it, use HTTP Basic Authentication with your API token as the "userid" and your API secret as the "password". You can find your API token and API secret by logging into your Jumio customer portal and navigating to the "Settings" page and clicking on the "API credentials" tab.

Header: The following parameters are mandatory in the "header" section of your request.

  • Accept: application/json
  • Content-Type: multipart/form-data
  • Content-Length: xxx (RFC-2616)

    The value for User-Agent must contain a reference to your business or entity for Jumio to be able to identify your requests. (e.g. YourCompanyName YourAppName/1.0.0). Without a proper User-Agent header, Jumio will take longer to diagnose API issues.

TLS handshake: The TLS protocol is required (see Supported Cipher Suites) and we strongly recommend using the latest version.

Note: Calls with missing or suspicious headers, suspicious parameter values, or without HTTP Basic Authentication will result in HTTP status code, 403 Forbidden.

Request Parameter

Note: Mandatory parameters are marked with an asterisk * and highlighted bold.

Parameter Type Max. Length Description
metadata * JSON Metadata of the customer's document as JSON objects, see table below
frontsideImage * JPEG or PNG Max. 5 MB Front side image of the customer's document
- if type = PASSPORT
- If type = ID_CARD or DRIVING_LICENSE and backsideImage not provided
backsideImage * JPEG or PNG Max. 5 MB Back side image of the customer's document if type = ID_CARD or DRIVING_LICENSE
Mandatory if frontsideImage not provided
type * String Possible types:
country * String 3 Possible countries:
- ISO 3166-1 alpha-3 country code
- XKX (Kosovo)

Response Parameter

Note: Mandatory parameters are marked with an asterisk * and highlighted bold.

Parameter Type Max. Length Description
scanReference * String Jumio’s reference number for each scan
type String Possible types:
issueDate String 255 Issue date in the format YYYY-MM-DD
issuingCountry String 3 Possible countries:
- ISO 3166-1 alpha-3 country code
- XKX (Kosovo)
originatingCountry Possible countries:
- ISO 3166-1 alpha-3 country code
- XKX (Kosovo)
number String 255 Identification number of the document
firstName String 255 First name of the customer
lastName String 255 Last name of the customer
dob String 255 Date of birth in the format YYYY-MM-DD
expiry String 255 Date of expiry in the format YYYY-MM-DD
optionalData1 String 255 Optional field of MRZ (TD1) line 1
optionalData2 String 255 Optional field of MRZ (TD1 and TD2) line 2
personalNumber String 255 Personal number field of MRZ (MRP)
street String 255 Street if type = DRIVING_LICENSE
city String 255 City if type = DRIVING_LICENSE
state String 255 State if type = DRIVING_LICENSE
postalCode String 255 Postal code if type = DRIVING_LICENSE
gender String 255 Possible values:
- M
- F

Optional parameters are returned:

  • If available on the ID
  • If readable
  • As readable (can be invalid)

Sample Request

Accept: application/json
Content-Type: multipart/form-data;boundary=----xxxx
Content-Length: xxx
Authorization: Basic
Content-Disposition: form-data; name="metadata"
Content-Type: application/json
"type": "PASSPORT",
"country": "USA"
Content-Disposition: form-data; name="frontsideImage"
Content-Type: image/jpeg
// Your image

Sample Response

"dob": "1990-01-01",
"expiry": "2022-12-31",
"firstName": "FIRSTNAME",
"issueDate": "2012-12-31",
"issuingCountry": "USA",
"lastName": "LASTNAME",
"number": "P1234",
"originatingCountry": "USA",
"personalNumber": "12345",
"scanReference": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
"type": "PASSPORT"

Supported IDs

The Fastfill API supports:

  • All Netverify supported passports

  • ID cards from the following countries: Albania, Argentina, Austria, Belgium, Bosnia & Herzegovina, Bulgaria, Canada, Cameroon, Chile, Czech Republic, Denmark, Dominican Republic, Ecuador, El Salvador, Estonia, Finland, France, Georgia, Germany, Guatemala, Hungary, Italy, Kazakhstan, Kenya, Latvia, Liechtenstein, Macedonia, Malta, Mexico, Moldova, Montenegro, Netherlands, Pakistan, Paraguay, Peru, Poland, Portugal, Romania, Serbia, Slovakia, Slovenia, Spain, Sweden, Switzerland, Turkey, United Arab Emirates, United Kingdom.

  • Driver licenses from the following countries: Austria, Belgium, Canada, Czech Republic, Denmark, Finland, France, Germany, Ireland, Italy, Netherlands, Poland, Portugal, Romania, Slovakia, Spain, Sweden, United Kingdom, United States.
    PDF417 bar code extraction from driver licenses back side from USA and Canada.

Supported Cipher Suites

Jumio supported cipher suites during the TLS handshake.

View Supported Cipher Suites

© Jumio Corp. 268 Lambert Avenue, Palo Alto, CA 94306

You can’t perform that action at this time.