openzeppelin_relayer::api::controllers::api_key

Function create_api_key

Source 
pub async fn create_api_key<J, RR, TR, NR, NFR, SR, TCR, PR, AKR>(
    api_key_request: ApiKeyRequest,
    state: ThinDataAppState<J, RR, TR, NR, NFR, SR, TCR, PR, AKR>,
) -> Result<HttpResponse, ApiError>
where
    J: JobProducerTrait + Send + Sync + 'static,
    RR: RelayerRepository + Repository<RelayerRepoModel, String> + Send + Sync + 'static,
    TR: TransactionRepository + Repository<TransactionRepoModel, String> + Send + Sync + 'static,
    NR: NetworkRepository + Repository<NetworkRepoModel, String> + Send + Sync + 'static,
    NFR: Repository<NotificationRepoModel, String> + Send + Sync + 'static,
    SR: Repository<SignerRepoModel, String> + Send + Sync + 'static,
    TCR: TransactionCounterTrait + Send + Sync + 'static,
    PR: PluginRepositoryTrait + Send + Sync + 'static,
    AKR: ApiKeyRepositoryTrait + Send + Sync + 'static,
Expand description

Create api key

§Arguments

  • api_key_request - The api key request.
    • name - The name of the api key.
    • allowed_origins - The allowed origins for the api key.
    • permissions - The permissions for the api key.
  • state - The application state containing the api key repository.

§Returns

The result of the plugin call.