API usage

Introduction

The data collected for the 2fa.directory website is also available as JSON files in order to enable developers to use it in their own programs. It is recommended to use the API with the highest version number, since older versions might not include all available information.

Caching

If you intend to query our JSON files often and with a lot of traffic, you may be blocked by Cloudflare, our reverse proxy provider. We therefore recommend that you cache the files locally for any large traffic cases.

Avoid downloading unnecessary data

If you only intent on using a specific dataset, like all sites supporting RFC-6238, we recommend that you use the URI which lists just that. See URIs for a list of available paths. The smaller the better.

Version 3

URIs

Coverage	Unsigned File	PGP Signed File
All sites	/v3/all.json	/v3/all.json.sig
All 2FA-supporting sites	/v3/tfa.json	/v3/tfa.json.sig
SMS	/v3/sms.json	/v3/sms.json.sig
Phone calls	/v3/call.json	/v3/call.json.sig
Email 2FA	/v3/email.json	/v3/email.json.sig
non-U2F hardware 2FA tokens	/v3/custom-hardware.json	/v3/custom-hardware.json.sig
U2F hardware tokens	/v3/u2f.json	/v3/u2f.json.sig
RFC-6238 (TOTP)	/v3/totp.json	/v3/totp.json.sig
non-RFC-6238 software 2FA	/v3/custom-software.json	/v3/custom-software.json.sig

Elements

Key	Value Type	Always Defined	Description
domain	FQDN	✔️	The domain name of the service
img	String		Image name used. If this is not defined, the image name is `domain`.svg
url	URL		URL of the site. If this is not defined, the url is https://`domain`
tfa	Array<String>		Array containing all supported 2FA methods
documentation	URL		URL to documentation page
recovery	URL		URL to recovery documentation page
notes	String		Text describing any discrepancies in the 2FA implementation
contact	Object		Object containing contact details. See table below for elements
regions	Array<String>		Array containing ISO 3166-1 country codes of the regions in which the site is available. If the site is available everywhere apart from a specific region, that region will be prefixed by a `-` symbol
additional-domains	Array<hostname>		Array of domains that the site exists at in addition to the main domain listed in the `domain` field.
custom-(software\|hardware)	Array<String>		Array of custom software/hardware methods that the site supports. Only present if the `tfa` element contains one of these 2FA types
keywords	Array<String>	✔️	Array of categories to which the site belongs

Contact Object Elements

Key	Value	Description
twitter	String	Twitter handle
facebook	String	Facebook page name
email	String	Email address to support
form	String	Support contact form
language	String	Lowercase ISO 639-1 language code for the site if it is not in English

Example website with 2FA enabled

[
  [
    "Site Name",
    {
      "domain": "example.com",
      "additional-domains": [
        "example.net"
      ],
      "tfa": [
        "sms",
        "call",
        "email",
        "totp",
        "u2f",
        "custom-software",
        "custom-hardware"
      ],
      "custom-software": [
        "Authy"
      ],
      "documentation": "<link to site TFA documentation>",
      "recovery": "<link to site TFA recovery documentation>",
      "keywords": [
        "keyword1",
        "keyword2"
      ]
    }
  ]
]

Example website with 2FA disabled

[
  [
    "Site Name", 
    {
      "domain": "example.com",
      "contact": {
        "twitter": "example",
        "facebook": "example",
        "email": "[email protected]"
      },
      "keywords": [
        "keyword1",
        "keyword2"
      ]
    }
  ]
]

Version 2

API version 2 is no longer available. If you use this version, please upgrade to version 3.

Version 1

API version 1 is no longer available. If you use this version, please upgrade to version 3.