TPS Checking API: How to Automate TPS and CTPS Checks for Your Business

Checking telephone numbers against the Telephone Preference Service (TPS) and Corporate Telephone Preference Service (CTPS) is an essential part of preparing UK outbound marketing campaigns.

But if your business processes hundreds or thousands of telephone numbers every month, manually checking calling lists can quickly become inefficient.

A TPS checking API allows businesses to automate telephone number screening, connecting TPS and CTPS checks directly to existing CRM systems, sales platforms and outbound diallers.

Instead of repeatedly uploading spreadsheets, your systems can check telephone numbers automatically, helping reduce manual work, maintain cleaner calling data and support compliance with UK telemarketing regulations.

In this guide, we'll explain how a TPS API works, how to integrate automated TPS checking into your business and how Data Soap can help.

What Is a TPS Checking API?

A TPS checking API is a software interface that allows businesses to automatically screen telephone numbers against the UK's Telephone Preference Service and Corporate Telephone Preference Service registers.

These registers allow individuals and businesses to indicate that they do not wish to receive unsolicited live sales and marketing calls.

A TPS API enables your software to submit telephone numbers for screening and receive structured results that can be used to manage your calling lists.

For example, instead of manually checking 5,000 telephone numbers before each campaign, a business could integrate an API into its CRM to check new contacts as they are added.

This makes it easier to manage telephone screening as part of an ongoing process rather than a separate administrative task.

At Data Soap, our TPS, CTPS and DNC checking service allows businesses to screen numbers against both preference registers, with API options for automated workflows.

How Does a TPS Checking API Work?

A TPS API connects your existing software to a telephone screening service.

When your system submits a telephone number, the API checks it against the relevant registers and returns the result.

The process typically involves four steps.

1. Submit a Telephone Number

Your CRM, dialler, lead management system or other application sends a telephone number to the API.

This might happen when a new lead enters your database, before a sales representative makes a call or as part of scheduled database screening.

2. Check Against TPS and CTPS

The submitted telephone number is compared against the relevant Telephone Preference Service and Corporate Telephone Preference Service records.

Data Soap maintains regularly updated TPS and CTPS screening data, helping businesses identify preference registrations without manually downloading and managing the registers themselves.

3. Receive the Screening Result

The API returns a structured response indicating whether the telephone number appears on the relevant preference registers.

Your software can interpret the response and store the result against the contact record.

4. Apply Your Calling Rules

Your system can then use the screening result to determine what happens next.

For example, a number registered with TPS could automatically be excluded from an unsolicited marketing campaign unless the business has established a valid exception.

Numbers without a TPS or CTPS match can move to the next stage of your calling eligibility checks, including your own suppression and consent records.

This automated process reduces the need for manual screening and can help prevent restricted numbers from entering outbound campaigns.

What Does the Data Soap TPS API Return?

One of the main advantages of using an API is that screening results can be returned directly to your software in a format developers can work with.

Data Soap's synchronous API supports TPS and CTPS checking through a single TPS lookup.

For example, a response from the API can look like this:

{
  "DataSoapAPIResponse": {
    "TPSResult": {
      "MSISDN": "00447976123456",
      "TPS": true,
      "CTPS": false,
      "DNC": true,
      "TPSID": 12032505
    }
  }
}

This is an illustrative response based on Data Soap's published API documentation.

The response includes the following fields:

Field	Description
MSISDN	Telephone number checked, in normalised format
TPS	Indicates whether the number is registered with TPS
CTPS	Indicates whether the number is registered with CTPS
DNC	Indicates whether the number matches the API's DNC screening data
TPSID	Screening result identifier

In the example above, the telephone number is registered with TPS, is not registered with CTPS and has a DNC match.

This information allows a business to apply its own suppression rules automatically.

Developers can find further technical information, including authentication and request formats, in the Data Soap synchronous API documentation.

What Are the Benefits of Automated TPS Checking?

For businesses that make regular outbound calls, integrating TPS screening through an API offers several practical advantages.

Reduce Manual Screening

Traditional bulk TPS checking involves preparing a spreadsheet, uploading the data, processing the results and updating the original records.

Although this works well for occasional campaigns, it can become repetitive when new leads are continuously entering your database.

An API allows screening to become part of your existing workflow, reducing the need to handle files manually.

Support Compliance With UK Marketing Regulations

Under the Privacy and Electronic Communications Regulations (PECR), businesses must respect registrations on the relevant telephone preference registers unless an applicable exception permits the marketing call.

Failing to follow the rules can result in complaints, investigations and enforcement action by the Information Commissioner's Office (ICO).

Automated screening can help identify registered numbers before they are used for unsolicited live marketing calls.

However, a TPS or CTPS check is not a complete compliance assessment. Businesses must also account for their own do-not-call records, relevant consent, previous objections and other applicable marketing rules.

Improve Calling List Quality

An outbound calling campaign is only as effective as the data behind it.

If sales teams are spending time on numbers that should have been excluded before dialling, the campaign becomes less efficient.

Automated TPS and CTPS screening helps businesses identify numbers requiring suppression or further review earlier in the process.

This can reduce unnecessary calling activity and help teams focus on appropriately screened records.

Keep CRM Records Updated

A telephone number that was not registered with TPS last month may be registered today.

This means businesses should not rely indefinitely on previous screening results.

By integrating TPS checking into your CRM, you can record screening outcomes and schedule repeat checks when appropriate.

For more information on maintaining accurate customer records, read our guide to GDPR Article 5 and data accuracy in your CRM.

How to Integrate TPS Checking Into Your CRM

One of the most common uses of a TPS checking API is integration with a Customer Relationship Management (CRM) system.

This allows businesses to automate screening as contacts move through the sales process.

For example, imagine your business collects leads through a website enquiry form.

A TPS API integration could work as follows:

1. A customer submits their telephone number through your website.

2. The telephone number is saved in your CRM.

3. Your system automatically submits the number to the Data Soap API.

4. The API returns the TPS and CTPS screening results.

5. Your CRM records the result, along with the date of screening.

6. Your software applies your business's calling eligibility and suppression rules.

This allows businesses to identify preference registrations early, before telephone numbers enter marketing workflows.

The same process could be used with lead generation software, internal databases, sales platforms and outbound dialling systems.

Businesses can also schedule repeat screening for existing records, rather than only checking new contacts.

TPS API vs Bulk TPS Checking: Which Is Better?

Both API and bulk screening have their place.

The best option depends on how frequently your business checks telephone numbers and how your calling data is managed.

Feature	TPS Checking API	Bulk TPS Checking
Screening method	Automated through software	Upload a CSV or Excel file
CRM integration	Yes	Manual import/export usually required
New lead screening	Can be automated	Usually performed in batches
Repeat checks	Can be scheduled	New uploads required
Technical development	Typically required	Not required
Best suited to	Ongoing screening	Periodic calling campaigns

For businesses checking an occasional list, using Data Soap's online portal may be the simplest solution.

However, companies running continuous lead generation, high-volume outbound sales or regular calling campaigns may benefit from a TPS API.

If you're preparing a specific campaign rather than an API integration, our guide explains how to check UK phone numbers against TPS and CTPS before a calling campaign.

Can You Check TPS and CTPS Through One API?

Yes. Data Soap supports TPS and CTPS screening within a single lookup.

This is particularly important for organisations conducting business-to-business marketing.

The Telephone Preference Service generally covers individual subscribers, including consumers, sole traders and certain partnerships.

The Corporate Telephone Preference Service covers corporate subscribers, including limited companies and limited liability partnerships.

A business-to-business calling database may contain numbers belonging to both types of subscriber.

For example, a campaign targeting small businesses might include numbers belonging to sole traders as well as limited companies.

Checking only CTPS could mean missing TPS registrations.

Our article on TPS vs CTPS: what's the difference? explains which register applies to different types of subscriber.

For businesses concentrating on B2B outbound calling, we also have a detailed guide to the Corporate Telephone Preference Service.

How Often Should TPS and CTPS Checks Be Performed?

Telephone preference registrations change over time.

New numbers are added to the registers, existing records change and businesses may receive direct objections to marketing.

For this reason, TPS checking should be treated as an ongoing process rather than a one-off exercise.

The 28-day period is important for UK telephone marketing. TPS and CTPS registrations generally take 28 days to become fully effective, and businesses should ensure their screening data is sufficiently current.

Many organisations use a 28-day rescreening cycle, with additional checks close to the point of calling where appropriate.

With an API integration, businesses can automate screening based on operational requirements.

For example, you might configure checks when:

• A new telephone number enters your CRM.

• A lead is added to an outbound calling campaign.

• An existing screening result becomes outdated.

• An older customer database is reactivated.

• A third-party lead list is imported into your system.

This helps businesses maintain a more consistent telephone screening process without repeatedly managing spreadsheets.

Can a TPS API Be Combined With Other Telephone Validation Checks?

Yes. TPS checking is only one part of maintaining a high-quality telephone database.

A business may also want to understand whether a telephone number is correctly formatted, whether it belongs to a mobile or landline, or whether a mobile number is active.

These checks answer different questions.

TPS and CTPS checking helps identify telephone numbers registered on the relevant marketing preference registers.

HLR lookup helps assess mobile number status and provides network-related information.

Landline validation helps assess the likely status of a UK landline.

For example, a telephone number could be active and technically valid but still registered with TPS.

Likewise, a number that is not registered with TPS could be disconnected or incorrectly formatted.

Data Soap's validation API documentation explains how developers can request multiple supported validation checks as part of an integrated data-quality workflow.

Combining the appropriate checks can help businesses improve calling data quality while supporting their telephone marketing procedures.

Who Should Use a TPS Checking API?

Automated TPS and CTPS checking is particularly valuable for businesses that process telephone numbers regularly.

Call Centres

Call centres managing large outbound campaigns can integrate TPS screening into their calling workflows, helping to identify restricted numbers before they reach agents.

Sales and Lead Generation Companies

Businesses generating leads from websites, advertising campaigns or external suppliers can check telephone numbers automatically as they enter their systems.

CRM and Software Providers

Developers can integrate TPS and CTPS screening into their own software, making preference checking available directly to users.

Marketing Agencies

Agencies managing outbound campaigns for multiple clients can use automated screening to maintain consistent processes across different calling lists.

Businesses With Large Customer Databases

Organisations maintaining thousands of customer or prospect records can use scheduled API checks to support regular screening without repeated manual uploads.

Why Use Data Soap for TPS API Checking?

Data Soap provides UK businesses with telephone screening and data validation services designed to improve data quality and support outbound marketing compliance.

Our TPS and CTPS checking service allows businesses to screen telephone numbers against both preference registers, with options for bulk processing and API integration.

By using Data Soap, businesses can benefit from:

• Combined TPS and CTPS checks: Screen against both registers in one lookup.

• API integration: Connect screening to your CRM, software or existing business workflow.

• Regularly updated screening data: Check numbers against updated preference-service records.

• Flexible usage: Use the online portal for bulk screening or an API for automation.

• Additional validation services: Access other Data Soap checks as part of your wider data-quality process.

Whether your organisation checks hundreds or thousands of telephone numbers each month, automating TPS screening can help reduce administrative work and make your outbound processes more consistent.

Start Automating TPS and CTPS Checks With Data Soap

If your business relies on outbound telephone marketing, checking calling lists shouldn't have to involve repetitive manual uploads.

A TPS checking API allows you to integrate telephone preference screening directly into your systems, helping you manage new leads, maintain your calling lists and apply suppression rules before campaigns begin.

Data Soap provides both bulk TPS checking and API-based screening, giving businesses the flexibility to choose the approach that suits their needs.

Ready to automate your TPS and CTPS screening?

Explore Data Soap's TPS, CTPS and DNC checking service or view our API documentation to learn how to get started.

Frequently Asked Questions

What is a TPS checking API?

A TPS checking API allows businesses to automatically screen telephone numbers against the Telephone Preference Service through their existing software, CRM or other applications. The API returns results that businesses can use to manage their calling data.

Does Data Soap offer TPS and CTPS checking through an API?

Yes. Data Soap supports TPS and CTPS screening through its API services. Businesses can integrate these checks into existing systems to automate telephone preference screening.

Can I integrate TPS checking into my CRM?

Yes. Developers can connect Data Soap's API to compatible CRM systems to perform checks when new telephone numbers are added, before campaigns or as part of scheduled screening workflows.

Can the TPS API check mobile and landline numbers?

Yes. Both mobile and landline telephone numbers can appear on the TPS and CTPS registers, so relevant numbers should be screened before unsolicited live marketing calls.

How often should I run TPS checks?

Businesses should ensure they screen against sufficiently current TPS and CTPS data and repeat checks as appropriate. A 28-day screening cycle is commonly used, with additional screening close to calling where necessary.

Is TPS checking required for B2B marketing?

The rules also apply to business-to-business live marketing calls. Depending on the subscriber, the telephone number may fall under TPS or CTPS. Businesses contacting mixed B2B audiences should generally consider checking both registers.

Does a successful TPS check mean I can legally call the number?

Not necessarily. A number that does not match TPS or CTPS may still be subject to an internal suppression request, previous objection or other legal restriction. TPS screening is one part of the broader calling compliance process.