Restricting access by IP adds an extra layer of security to your integration with Cobre. Once it is enabled, only requests coming from the IPs you register can reach your API credentials and your Portal users.This guide explains what you need to have ready before requesting a change, so the process is quick and simple. Once your ticket is created, the change is applied within 2 to 6 hours.
Before you start#
Review these six points. If you have all of them covered, your request is ready to be submitted.1. Whitelisting applies to both API and Portal#
IP whitelisting is configured at the same time on your API users and on your Portal users. It cannot be applied to only one of them.After the change, your Portal users will only be able to sign in from the IPs on the list. If anyone on your team connects from other networks (home, VPN, other offices), include those IPs in your request as well.
2. Every change is registered in a ticket#
Adding, removing or replacing IPs is always managed through a ticket sent to soporte@cobre.co. Requests received through Slack, email threads or calls are executed once the ticket exists.3. Only IPv4 is supported#
We need the public outbound IPv4 address of your servers. IPv6 addresses are not supported, neither alone nor mixed with IPv4. If your infrastructure only has IPv6, your network provider can assign you a fixed IPv4 address.| Format | Example | Supported |
|---|
| IPv4 | 190.85.12.34 | ✅ |
| IPv6 | 2800:e2:4c80::1 | ❌ |
4. Maximum of 98 IPs in total#
The limit is the sum of the IPs you already have configured plus the ones you want to add. If you exceed it, tell us which IPs to remove.Ranges count every address they contain:| Range | /32 | /30 | /29 | /28 | /26 | /25 | /24 |
|---|
| IPs | 1 | 4 | 8 | 16 | 64 | 128 (exceeds the limit) | 256 (exceeds the limit) |
If your network uses a large range, send a smaller range or the specific IPs instead.5. The change takes 2 to 6 hours#
The time is counted from the moment the ticket is created. If you have a go-live date or an integration in progress, open the request ahead of time.Each environment has its own configuration. If you need the same IPs in QA and in Production, open two tickets, one per environment.| Ticket | Environment |
|---|
| Ticket A | QA only |
| Ticket B | Production (PRD) only |
What to include in your request#
The environment where the change will apply: QA or PRD
Whether you want to add, remove or replace IPs
The list of IPs in IPv4 format, including the ones your team uses to access the Portal
Confirmation that your current IPs plus the new ones do not exceed 98
Frequently asked questions#
Can I apply whitelisting only to the API and leave the Portal open?#
No. The restriction always applies to both. Make sure the list includes the IPs your team uses to sign in to the Portal.I already sent my request by email. Is it ready?#
To execute it we need a ticket. Register it with the same information and the process starts from there.My provider gave me an IPv6 address. Can you add it?#
For now we only support IPv4. Ask your provider for the public outbound IPv4 address.Can I add the range 181.49.20.0/24?#
That range equals 256 IPs and the maximum is 98. Send a smaller range or the specific IPs.It is urgent. Can it be ready in 30 minutes?#
The process takes between 2 and 6 hours from the moment the ticket is created.Can I request QA and Production in a single request?#
They are handled as two requests, one per environment.