Yes No
Login to see more...
You must be logged in to see notifications.
You are using the new API (3) - New security API's.


Here at DACCAA, we love developers.

We have updated the API to a new standard. This standard is based on OAuth. You will need to get an access_token in order to access information on a user. Please use the information below to see how to use it.

Register your app

Firstly, register your app. To do this, select My Key (or Request Key) and then follow instructions to create a new app.

Your logo should be a familar logo to your users and should be provided in URL form.

The redirect URI is where we will send back all requests depending on user action. It is recommended if you want different exit locations, you should register more then one app.

To make the login button

To make the login button simply make a link to https://daccaa.com/developer/v3/access_token.php?clientID=12345 of course with the clientID being your actual client ID found within the app area.

Successful authorisation will result in the return of an access_token and id.

If the user declines it will return error=declined in the get parameters.

Time to request...

Use the Client Secret, Access Token and User ID to make a full request. Requests are made to https://daccaa.com/developer/v3/?client_secret=12345&access_token=12345&id=01 these should be made server-side to not expose your client_secret.

You may find that you get some errors, most are self explanatory - but if you need help contact support where we are more then happy to help.

Thoughts and implementations

Before we get onto any examples, I would like to take this time to discuss applications for the use of the DACCAA API as there has been several different examples where people have found use for the DACCAA API. Here are just some examples:

  • Login with DACCAA (see below)
  • An autofill method for information - DACCAA makes sharing your information seemless so it is easy to create a autofill with DACCAA button.
  • Contact using DACCAA information

Login with DACCAA

I want to spend some time elaborating on the login with DACCAA method as it was designed with a certain focus in mind. The user flow would be something like:

  • The user visits your website
  • The user clicks either login or register
  • The user sees the login with DACCAA button (on both register and login page)
  • The user clicks the button and is sent to the authorisation page (as they are already logged in - likely as DACCAA remembers them)
  • The user then clicks "authorise" and is taken back to your site

Now lets stop there because this is where the system ideology starts to form.

If the user has an account but has not associated it with their DACCAA account then this process would make the association and then log them in.

If the user has an account that has been associated then it will just log them in.

If the user has never visited this website before then an account is created and the associated is made - the user has the oppertunity to create a password later on or just use DACCAA to login everytime - usernames can also be generated by using hashed emails or any value you like which is then shortened and added to their firstname.)

So what are we checking when we say they already have an account? We are checking the email addresses, we make the assumption that as DACCAA verifies all email addresses and has options for 2FA (two factor authentication) then we will be pretty sure that the person we are sending over to you is the person who it is meant to be.

Brand Values and Rules

As you may expect we have certain values and expectations for the usage of our members system. You must do the following:

  • Always contain the on any form that is a login form for DACCAA. https://daccaa.com/search/letter_d.png
  • You can place buttons with the following, "Login with DACCAA", "Autofill with DACCAA" or "Register with DACCAA".
  • Any button that uses the API must be styled like so:

  • .DACCAAbutton { padding: 20px; padding-left: 50px; background-color: #def; border-radius: 3px; color: #0099cc; text-decoration: none; display: inline-block; min-width: 208px; background-image: url("https://daccaa.com/Storage_new/2016/daccaaLogoD.png"); background-repeat: no-repeat; background-size: 30px 30px; background-position: left 10px center; border: solid 1px #0099cc; font-weight: bold; font-family: "HelveticaNeue-Light", "Helvetica Neue Light", "Helvetica Neue", Helvetica, Arial, "Lucida Grande", sans-serif; } .DACCAAbutton:hover { background-color: #0099cc; background-image: url("https://daccaa.com/drive/uploads/49/kgvnx8i3x9ngiw7ceoizk91a5xpl51/darkLogo.png"); color: white; }
  • Do not place anything on the login in page that suggests that it is not linked to DACCAA.
  • Do not state that DACCAA is a partner/sponsor or any other non such affiliate.
  • Always include a link to the DACCAA sign up page. https://daccaa.com/login/register.php
  • You may use the DACCAA hex colours: #0099cc and #006699.
  • You may also use the marketing "Works with DACCAA" image (https://daccaa.com/aa/share.php?member=49&id=302&code=1611955315&access=899335790).


Did we make a mistake? Do you think there is any vulnerabilites with this? Or are you still confused? Then get in touch with us and we will aim to reply with 48 hours for the quickest support possible.

contact us

Copyright © Danny Franklin 2021.