Systems and methods for facilitating authentication for an entity system to use a partner system using pooled identifiers
Some embodiments involve systems and methods for facilitating authentication for an entity system to use a partner system using pooled identifiers (e.g., without requiring the entity system to first register with the partner system). In some embodiments, based on (i) a request, from a first entity system, indicating a first partner system to process at least a part of an operation and (ii) an indication that the first entity system is not registered for use of the first partner system, a platform system may link a first authentication identifier of the first identifier set with the first entity system. The platform system may process the operation using the first authentication identifier linked by the platform system with the first entity system, and the platform system may use platform authentication data established with the first partner system to authenticate the platform system to the first partner system for performing the operation.
1 . A platform system for facilitating application programming interface (API) authentication for an API entity system to use an API partner system using pooled authentication identifiers without the API entity system first registering with the API partner system, the platform system comprising:
one or more processors and non-transitory media storing instructions that, when executed by the one or more processors, cause steps comprising:
storing, at the platform system, a pool of authentication identifiers comprising (i) a first third-party identifier set having authentication identifiers pre-allocated by a first third-party API partner system for use by the platform system and (ii) a second third-party identifier set having authentication identifiers pre-allocated by a second third-party API partner system for use by the platform system;
based on (i) an API request, from a first API entity system, indicating the first third-party API partner system to process at least a part of an operation and (ii) an indication that the first API entity system is not registered for use of the first third-party API partner system, linking a first third-party authentication identifier of the first third-party identifier set with the first API entity system; and
without first registering the first API entity system with the first third-party API partner system, processing the operation using the first third-party authentication identifier linked by the platform system with the first API entity system, the platform system using platform authentication data established by the platform system with the first third-party API partner system to authenticate the platform system to the first third-party API partner system for performing the operation.
2 . The platform system of claim 1 , the steps further comprising:
after completing the processing of the operation using the first third-party authentication identifier, initiating asynchronous registration of the first API entity system to the first third-party API partner system using entity account information associated with the first API entity system.
3 . The platform system of claim 1 , the steps further comprising:
monitoring a size or usage level of the first third-party identifier set; and
sending, based on the size or usage level falling below a replenishment threshold, a replenishment request for additional authentication identifiers to the first third-party API partner system.
4 . The platform system of claim 1 , wherein linking the first third-party authentication identifier of the first third-party identifier set with the first API entity system comprises retrieving, based on an inferred request parameter of the API request indicating the first third-party API partner system, the first third-party authentication identifier from the first third-party identifier set for the first API entity system.
5 . The platform system of claim 1 , wherein linking the first third-party authentication identifier of the first third-party identifier set with the first API entity system comprises updating an entity account in an account datastore of the platform system to store an association between the entity account and the first third-party authentication identifier.
6 . The platform system of claim 1 , the steps further comprising:
based on the first API entity system later submitting a subsequent API request indicating the first third-party API partner system to process at least a part of a second operation, reusing the first third-party authentication identifier previously linked to the first API entity system to process the second operation.
7 . The platform system of claim 1 , wherein:
receiving the API request at the platform system comprises receiving, at an application programming interface endpoint of the platform system, a platform-API-based message using platform APIs of the platform system; and
processing the operation comprises sending, to the first third-party API partner system, partner-API-based messages using partner APIs of the first third-party API partner system.
8 . The platform system of claim 1 , wherein the platform system acts as a proxy between the first API entity system and the first third-party API partner system by authenticating the first API entity system to the platform system using entity authentication data associated with the first API entity system and authenticating the platform system to the first third-party API partner system using the platform authentication data.
9 . The platform system of claim 1 , wherein determining that the first API entity system is not registered for use of the first third-party API partner system comprises determining whether an identifier associated with the first API entity system in an account datastore is associated with a third-party authentication identifier for the first third-party API partner system.
10 . The platform system of claim 1 , wherein, before the API request from the first API entity system is received by the platform system, the first third-party authentication identifier is already activated by the first third-party API partner system as an active authentication identifier for use by the platform system.
11 . A method comprising:
storing, at a platform system, a pool of authentication identifiers comprising (i) a first third-party identifier set having authentication identifiers pre-allocated by a first third-party partner system for use by the platform system and (ii) a second third-party identifier set having authentication identifiers pre-allocated by a second third-party partner system for use by the platform system;
based on (i) a request, from a first entity system, indicating the first third-party partner system to process at least a part of an operation and (ii) an indication that the first entity system is not registered for use of the first third-party partner system, linking a first third-party authentication identifier of the first third-party identifier set with the first entity system; and
processing the operation using the first third-party authentication identifier linked by the platform system with the first entity system, the platform system using platform authentication data established by the platform system with the first third-party partner system to authenticate the platform system to the first third-party partner system for performing the operation.
12 . The method of claim 11 , further comprising:
after completing the processing of the operation using the first third-party authentication identifier, initiating asynchronous registration of the first entity system to the first third-party partner system using entity account information associated with the first entity system.
13 . The method of claim 11 , wherein linking the first third-party authentication identifier of the first third-party identifier set with the first entity system comprises updating an entity account in an account datastore of the platform system to store an association between the entity account and the first third-party authentication identifier.
14 . The method of claim 11 , further comprising:
based on the first entity system later submitting a subsequent request indicating the first third-party partner system to process at least a part of a second operation, reusing the first third-party authentication identifier previously linked to the first entity system to process the second operation.
15 . The method of claim 11 , wherein the platform system acts as a proxy between the first entity system and the first third-party partner system by authenticating the first entity system to the platform system using entity authentication data associated with the first entity system and authenticating the platform system to the first third-party partner system using the platform authentication data.
16 . The method of claim 11 , wherein determining that the first entity system is not registered for use of the first third-party partner system comprises determining whether an identifier associated with the first entity system in an account datastore is associated with a third-party authentication identifier for the first third-party partner system.
17 . The method of claim 11 , wherein, before the request from the first entity system is received by the platform system, the first third-party authentication identifier is already activated by the first third-party partner system as an active authentication identifier for use by the platform system.
18 . One or more non-transitory computer-readable media storing instructions that, when executed by one or more processors, cause steps comprising:
storing, at a platform system, a pool of authentication identifiers comprising (i) a first identifier set having authentication identifiers pre-allocated by a first partner system for use by the platform system and (ii) a second identifier set having authentication identifiers pre-allocated by a second partner system for use by the platform system;
based on (i) a request, from a first entity system, indicating the first partner system to process at least a part of an operation and (ii) an indication that the first entity system is not registered for use of the first partner system, linking a first authentication identifier of the first identifier set with the first entity system; and
processing the operation using the first authentication identifier linked by the platform system with the first entity system, the platform system using platform authentication data established by the platform system with the first partner system to authenticate the platform system to the first partner system for performing the operation.
19 . The one or more non-transitory computer-readable media of claim 18 , the steps further comprising:
after completing the processing of the operation using the first authentication identifier, initiating asynchronous registration of the first entity system to the first partner system using entity account information associated with the first entity system.
20 . The one or more non-transitory computer-readable media of claim 18 , wherein, before the request from the first entity system is received by the platform system, the first authentication identifier is already activated by the first partner system as an active authentication identifier for use by the platform system.