Developer Portal

To access miiCard Identity Claims and Financial APIs you need to configure an API key and secret. If we have enabled your account for self-management you can do this yourself, otherwise please register for developer access below.


Request Developer Access

Please let us know if you plan to use

  • WS-Federation
  • Windows Azure ACS

so we can configure your account accordingly.

Once we take a look at your request we will set up a key and secret and you can start to use the APIs either manually, or using one of our drop-in components or wrapper libraries.

To use the Directory API you do not need tokens or authentication information - just check out the documentation and get started!


If you have any questions about integrating miiCard please contact us at :



What information can I request from a miiCard member?

At present you can request any information that a miiCard member can also publish to their public profile page - we call these 'public claims'. The member doesn't have to have published their public profile for you to request data from them - it might be that they want to keep their profile private but elect to share certain information with certain sites. These are:

  • Their name (which is always supplied)
  • An email address - if they have multiple, they'll be asked to select a single email address
  • A phone number - if they have multiple, they'll be asked to select a single phone number
  • A postal address
  • Date of birth
  • Social media and other internet identities
    • Facebook
    • LinkedIn
    • Twitter
    • Google+
    • Microsoft LiveID
    • eBay

We also provide a boolean flag indicating whether the miiCard member's identity has been assured, which shows that they have associated a financial account with their miiCard account to verify their name and identity. We call this the member's 'level of assurance'.

Subscription vs Transactional Charging Model

miiCard offer two ways to consume the identity details of our members; the subscription model and the transactional model:

  • Only miiCard members with a premium subscription can share their identity with your application under the subscription model, but you aren't charged
  • Any miiCard member can share their identity through the transactional model, but you'll be charged the first time each member does so

For more information on the differences and which use-cases each model enables, see the Types of Access page.

Contact us for pricing information »

What next?

The easiest way to consume miiCard identity details is to use one of our wrapper libraries or drop-in components. If you don't see a library targeting your desired programming language, or a component for your preferred development framework then drop us a line and we'll get back to you.

You can also consume our API manually, using the SOAP, XML or JSON endpoints - our Claims API documentation details how to make an API call and what sort of responses to expect. You can also see some demonstrations of miiCard in use for inspiration.