Endpoints

Account management

  • 1001: Create accountCreates a new entity/user account in the Rubiq database with fields specified in a contract between the calling application and the Rubiq platform. A unique Rubiq entity ID is automatically assigned to the new entity, and optionally a key with an external type.
  • 1002: Get account dataRetrieves data for an entity/account. The returned data will always contain the Rubiq entity ID and optionally a key with an external type. In addition, the payload contains the data specified in the contract between the calling application and the Rubiq API.
  • 1003: Update account dataValidates that the data complies with possible rules and performs the update if it does. Only the data provided in the payload is updated. The calling application must have permission to update accounts.
  • 1004: Remove accountDeletes an entity/account. The calling application must have permission to delete accounts.
  • 1005: Create childCreates a new entity/account as a child of another entity in the Rubiq database, with fields specified in a contract between the calling application and the Rubiq API. The parent-child relationship between the entities must be previously established in Rubiq Cloud.
  • 1006: Enumerate childrenRetrieves all the children for an entity/account. The returned data will always contain the Rubiq entity ID and optionally a key with an external type for each of the children. In addition, the payload may optionally contain the data for each child as specified in the contract between the calling application and the Rubiq API.
  • 1007: Connect to trackConnects an entity/account to a track
  • 1008: Disconnect from trackDisconnects an entity/account from a track. The connection between the entity and the track is not removed, but the state is changed to "disconnected".
  • 1009: Enumerate tracksRetrieves an enumeration of all the tracks an account is connected to.
  • 1010: Determine track connectionDetermines if an account is connected to a track 
  • 1011: SearchSearches the entire Rubiq database for accounts which match a given search string.
  • 1050: Evaluate loyalty schemeEvaluates a loyalty scheme for an entity
  • 1012: Create changed since sessionBegin a search session to find all Rubiq entities that have been modified since a given date, and return the session token identifier.
  • 1013: Get changed sinceReturn entities for a search session specified by a token identifier.
  • 1020: Create account with childrenCreates a new user entity and child entities in a single request. This endpoint is a combination of endpoints 1001: Create account and 1005: Create child.

Account authentication

  • 2001: AuthenticateAuthenticates an entity by checking whether, for example, the submitted username and password matches the data in the database, or a specific account on a social media is registered in the database.
  • 2002: Change passwordUpdates password of an entity after first having verified that the old password is correct and matches entity
  • 2003: Trigger “Forgotten password” serviceInitiates communication flow when a user has forgotten their password. What specifically happens must first be configured in Rubiq Cloud.
  • 2004: Verify accountActivates an entity/account, when the contract specifies that all new entities must be verified before they can be used.
  • 2005: Request onetime-passwordRequests that the API generate a onetime-password to be emailed to an entity email address. The password can then be used to authenticate using authType: onetime, with endpoint 2001: Authenticate.

Social connections

Mobile devices

  • 4001: Register mobile deviceRegisters a mobile device to an entity. Registration may optionally contain information about the device token for dispatch of push messages. This end point should be called once every time the mobile app is started. 
  • 4002: Sign out mobile deviceTurn off push messaging for a device until it is registered again
  • 4003: Get deviceFetches the mobile device details.  For iOS, this will only ever be the device id. For other device types (Android, WindowsPhone, Windows8 and BlackBerry), the current "push" status is also included, indicating whether push communications may be sent to this device.

Transactions

  • 5001: Register a transactionStores information about a transaction made by a person. A transaction may for instance be some kind of action, a purchase, redemption of a coupon or a transaction on a points account or cash account
  • 5002: Has transactionReturns a boolean value indicating whether a transaction has been logged for the user with a specific group and type - optionally filtered by time period.
  • 5003: Sum transactionsReturns a sum total of the transactions for a user in a specific transaction group, optionally filtered by transaction type and time period.
  • 5004: Enumerate transactionsRetrieves transactions that have been logged for the user with a specific group - optionally filtered by type and time period, with "paging" options (limit and offset)

Miscellaneous services

Communication

Forms

Content

  • 9001: Create contentAdd tagged content to the system. The content must be published using endpoint 9003: Publish content before it can be accessed.
  • 9003: Publish contentPublish content, making it available to be used in search results.
  • 9005: Public content searchSearch for publicly available content
  • 9006: Enumerate tagsFetch a list of all tags
  • 9002: Connect entityConnect an entity to content. Once content has been connected to at least one entity, it is considered "private", and can only be accessed by entities that have been connected to it.
  • 9004: Private content searchSearch for content available to a specific entity. The result may also include public content.
  • 9007: Remove contentRemove a tagged content item. Individual content items may be removed from the system, when they can be uniquely matched on tags and data.
  • 9002: Connect multiple entitiesConnect an array of entities to content.
  • 9008: Reconnect entitiesReplace the currently connected entities with a new array of entities. All previous connections will be removed for the content and the new array of entities connected instead.

Media

Documents

Terms and Permissions

Loyalty

Entity Preferences

Lead management

  • 1100: Create leadCreates a new Lead entity. The leadSourceID and all fields are configured within the Rubiq Lead Management app.
  • 1101: Get lead source fieldsReturns the required and optional fields used in Lead creation.

Lotteries

  • 9400: Get active lotteryReturns the currently active lottery. If no lottery is currently active, a 404 response is returned.
  • 9402: Create reservationReserve a package of lottery numbers for a limited time.
  • 9403: Cancel reservationCancel a reservation of lottery numbers, making them available to others to purchase.
  • 9404: Pre-approve reservationPre-approve a reservation of lottery numbers, extending the reservation expiry time and preparing the reserved numbers for purchase. 
  • 9405: Approve reservationApprove a reservation of lottery numbers. The reservation is marked as approved and a purchase is initiated with a 3rd-party payment provider.
  • 9406: Approve paymentRegister the completed payment and complete the purchase.
  • 9407: Discard paymentRegister a cancelled or discarded purchase of a lottery number reservation.
  • 9401: Get upcoming lotteryReturns the next lottery which will become active in the future. If no upcoming lottery exists, a 404 response is returned.