Skip to content
Hablame Developers menu
Create your API keyOpens in a new tab

API changelog

What changed in the API, with its date. Only what has a verifiable source is recorded.

How to read this page

Each change carries its real date. A change that may affect your integration is marked “Change”; the rest is something new or an adjustment to this documentation.

  1. Change

    Number Lookup requires its service on the key

    Looking up numbers no longer works with any valid key: the key needs the Number Lookup service.

    • The /api/v6/numberinsight/* routes require the numberinsight service, which Cloud shows as “Validación de números” (Number Lookup). Without it, they answer 403 AUTH_SERVICE_NOT_ALLOWED.
    • If your integration looks up numbers, ask the owner of your organization for a key with that service. How lookups are charged does not change.

  2. Change

    Each service on a key is granted in full, and only the owner creates keys

    A key’s permission over a service is all or nothing. Capabilities remain only for the account.

    • The urlshortener.write and storage.files capabilities are retired. Only account and directory, which belong to the account, remain.
    • The urlshortener service grants the whole URL shortener: listing and reading, and also creating (each creation is charged), editing, deleting and restoring links. The storage service grants the seven Storage queries, files and downloads included; without it, the seven answer 403 AUTH_SERVICE_NOT_ALLOWED.
    • Only the owner of the organization creates API keys. Who can delete them does not change: whoever created it, the owner or an administrator.

  3. Documentation

    The reference shows only what works

    The public reference now documents the 22 endpoints that respond today, and the rest stop appearing.

    • Published are the URL Shortener (11 endpoints), Storage (7, all read-only), the organization query, the country catalog (2) and the ping.
    • The endpoints of services that are not open yet, and those that answer 501 NOT_IMPLEMENTED, no longer appear in the reference, in OpenAPI or in Postman.
    • The Number Lookup webhooks page is retired and redirects to the webhook events.

  4. New

    Storage can be queried through the API

    Seven new queries to see what you store, its usage, retention and price, and to list and download your files.

  5. New

    URL Shortener: bulk creation, safe retries and restoring

    A set of URL Shortener changes, approved after its September 30 audit.

    • New: create up to 1,000 links in one request, with one result per link.
    • The Idempotency-Key header returns to link creation and to the batch: a retry does not create or charge twice. See Idempotency.
    • The list paginates by cursor with no cap, and its total is exact up to 10,000.
    • New: restore a deleted link for 90 days, with no new charge.
    • New blocked status for links that Hablame blocks for security, and a new domainStatus field that says whether the domain lets the link open.
    • With a monthly URL Shortener plan there is a daily creation quota (URLSHORTENER_LINK_QUOTA_EXCEEDED).
    • More dangerous destinations are rejected, and on shared domains so are aliases that imitate a brand, a bank or a public entity. Own domains that are not verified are no longer offered to create links.

  6. Change

    Writing in the URL Shortener requires a separate capability

    Creating, editing, deleting and restoring links requires the urlshortener.write capability; querying still requires only the service.

    • Until that date, any key with the urlshortener service could create, redirect and delete all the organization’s links. Writing now requires urlshortener.write, which only an owner or an administrator grants when creating the key.
    • URL Shortener keys issued before that change received the capability, so they keep writing as before. A key without it answers 403 AUTH_CAPABILITY_NOT_ALLOWED when writing.

  7. New

    API keys with allowed networks

    A key can be created to work only from certain IPs or IP ranges.

    • When creating a key in Cloud you can set up to 20 IPs or ranges. From any other network, the API answers 403 AUTH_IP_NOT_ALLOWED.
    • The IP the API saw your request come from comes in meta.clientIp of every response. The list cannot be changed after the key is created.

Need help?

Was this page helpful?

See all support channels