Last updated: 27.05.2025
Download OpenAPI specification:

Introduction

ConnectID is a solution for user authentication, authorization and payment for web pages and apps. ConnectID is made by Unite AS.

Parties

The main parties using ConnectID are:

Partners: The organization publishing a web site, an app, a newspaper, a magazine, a newsletter or any other information users shall have access to. A partner will often have only one site, but may have many.

Clients: A client is a third-party website or app that uses ConnectID. A client may serve information for one or more newspapers, magazines, newsletters or other similar products. It may also have discussion forums and other services a user is able to access. The information may be available without a login or require a login. It may be available free or only if paid for. The services described here makes login (authentication) and user authorization available to a site to make it able to present only the authorized information to any user. Each client must have a unique clientId.

Users: Any end user with access to information. This may be a reader, a subscriber or someone who orders something. It may also be someone who takes part in a discussion and where it necessary to log in before posting.

Versioning

The services will be regularly upgraded. As a general rule this should not be an issue for the client. All existing elements will be present in new versions. New elements may be added. Your application may safely ignore new elements.

If there are major changes to a service it will normally be developed as a new endpoint with the new / changed functionality. The old version will be available to other clients that are not upgraded to the latest version. New clients should always use the newest version.

Services may be dropped if there are no known clients using it or if the service is not compatible with changes to the core system. Client developers will be notified if this should happen.

ConnectID specifications

URLs

ConnectID can be used with new domain servers, which one have better names and link structure. For now there are two different servers for Norway and Sweden.

connectid.no

connectid.se

Server

There are currently two types of servers in use, namely the loginServer and the apiServer.

loginServer

Production: https://connectid.no/user/ or https://connectid.se/user/

Test: https://api-test.mediaconnect.no/login/ (Note the /login/ path at the end)

apiServer

Production: https://api.mediaconnect.no/capi/

Test: https://api-test.mediaconnect.no/capi/

Configuration for new client in ConnectID

The minimum configuration to create a new client in ConnectID are listed below:

Client logo

Client background

Name

Name description

Homepage URL

Customer Care phone number

Customer Care e-mail address

Product

Subscription terms url

User terms url

Client Logo

Its very important that client logo is in a good quality. Best if has transparency when needed. Acceptable formats are:

.svg

.png

.jpg

Dimension of the logo image should be at least (for best view):

width: 318 px

height: 64 px

Client background

In ConnectID client can customize background that is displayed behind the gui. It should be ratter big like 2835x2126 px. Background is displayed as a “cover” for whole window. Information about size and way to display are specified in custom.css.

custom.css:

It is possible to introduce new look using custom.css. Here can be override all other styles, background images, fonts etc. which one are used in standard login.css.

Default custom.css:

For example can be easy changed colors of the headings…

About the API

The WebServices provided by Unite AS are developed as a REST-like API, see this wikipedia article about REST will give you an introduction to REST. Most modern programming languages have support for consuming REST services or have libraries that can be used.

Access the API using the apiServer

This server hosts the APIs. It has the following address:

Production: https://api.mediaconnect.no/capi/

Test: https://api-test.mediaconnect.no/capi/

Response header

A response header is used to provide additional information. We are using following custom response header.

Response header	Description
X-Mediaconnect-Api-Version	The project version this response is based upon
X-RateLimit-Remaining	A rate limit is the number of API calls you may do within given time period. If this rate limit is exceeded, your API-calls will be throttled. The number of request remaining before encountering a 429 too many request error. Our for a client is: • 100 API calls for a second. • 2000 API calls for a minute.
X-RateLimit-Reset	A rate limit is the number of API calls you may do within given time period. If this rate limit is exceeded, your API-calls will be throttled. The remaining epoch seconds before the rate limit resets. Renew every 60 seconds.

About the Client Mode

Some API endpoints are available to the client without an access token created by the user. Instead the client can request an access token on behalf of the client itself. Some of the services described under this section may be cached by the client for a limited time. The resources will in many instances be quite static, but changes may happen at any time. A long cache timeout can be used if the partner can invalidate the cache on demand.

Access the API using the apiServer:

Production: https://api.mediaconnect.no/capi/

Test: https://api-test.mediaconnect.no/capi/

Connect/ConnectID API Reference

Introduction#

Parties#

Versioning#

ConnectID specifications#

URLs#

Server#

Configuration for new client in ConnectID#

Client Logo#

Client background#

About the API#

Response header#

About the Client Mode#

Introduction

Parties

Versioning

ConnectID specifications

URLs

Server

Configuration for new client in ConnectID

Client Logo

Client background

About the API

Response header

About the Client Mode