Skip to main content

Home › Resources › Glossary › Application programming interface (API)

Application programming interface (API)

An application programming interface, or API, is a defined way for one piece of software to request information or actions from another. It enables systems to exchange data without someone copying it manually between screens.

← Back to all glossary terms

A   B   C   D   E   F   G   H   I   J   K   L   M   N   O   P   Q   R   S   T   U   V   W   X   YZ

Page at a glance

  • Meaning: API stands for application programming interface.
  • Purpose: Connect software through defined requests and responses.
  • Typical use: Exchange information or trigger authorised actions.
  • In DAM: Retrieve assets and metadata from other systems.
  • Security: Authentication and permissions still apply.

HOW IT WORKS

How an API works

An API defines what requests a software application can make and what responses to expect.

  1. An authorised application sends a request using an agreed method and credentials.
  2. The receiving system checks the request and permissions.
  3. It returns information, confirmation or an error.
  4. The application uses that response in its workflow.

An API is not itself a complete integration. Configuration, licensing and security controls still matter.

IN PRACTICE

Using APIs with digital asset management

A content management system (CMS) could use an API to request details of an approved brand image from a digital asset management (DAM) system. An editor can then select the correct asset rather than downloading and uploading another copy.

Asset Bank documents a REST API for asset searches, retrieval and metadata operations. Availability depends on subscription and configuration. API access must respect permissions and content usage rules.

What should a marketing team check before reuse?

  • Identify which assets and information the application needs.
  • Authenticate using the supported method and limited permissions.
  • Test permitted operations and verify responses.
  • Handle errors, content changes and usage restrictions.

ILLUSTRATIVE EXAMPLE

A catalogue connected to a DAM

Illustrative example, not a customer result. A catalogue system asks a DAM for an approved product photograph and its descriptive metadata, then presents the result for an editor to review before publication.

The connection may reduce repeated file handling, but the editor still needs to check that the image is current and approved for the intended use.

Frequently asked questions

Is an API the same as an integration?

No. An API provides an interface; an integration is a particular working connection built using that interface and potentially other services.

Do APIs bypass file permissions?

They should not. Access depends on the authentication and permissions configured for the application or user. Those controls need to be checked when setting up a connection.

Does Asset Bank offer an API?

Yes. Asset Bank documents a REST API for searches, retrieval and metadata operations. Its support documentation describes API availability for Professional and Enterprise subscriptions and recommends OAuth 2.0. Verify the organisation's subscription and settings before promising a specific integration.

Is an API always public?

No. APIs may be internal, limited to partners or exposed to outside developers with authentication and permission checks.

See Asset Bank in action

Explore how Asset Bank helps marketing teams manage, control and share digital assets.

KEEP EXPLORING

Related terms and reading

Sources and further reading