In IBM API Connect v10.0.3, rate limiting for APIs can be defined in two primary places: Plan and Catalog .

Plan : Rate limiting is typically defined at the Plan level. A Plan in API Connect specifies how an API or a group of APIs is exposed to consumers. It can include rate limits, quotas, and other restrictions. Defining rate limits at the plan level ensures that each application subscribed to the plan adheres to the specified API consumption limits, such as the number of API calls allowed within a given time period.

Catalog : The Catalog is another place where rate limits can be defined. A Catalog represents a collection of APIs and their configurations, including security and rate limiting policies. Rate limits defined at the Catalog level apply globally to all APIs and applications within that Catalog, providing an overarching control mechanism to enforce consumption limits across different APIs.

These two locations allow flexibility in controlling API usage, either by restricting usage per plan (at a more granular level) or globally across all APIs within a catalog.

References:

IBM API Connect v10.0.3 - Now Available

IBM API Connect Documentation

$ref Usage : The $ref keyword is used in OpenAPI (formerly Swagger) specifications to reference reusable components, such as schemas, parameters, and responses, defined elsewhere in the document or in external files.

Replacement Mechanism : When an API is published, the $ref is processed and replaced with the actual contents of the referenced file or component. This allows for modular and maintainable API definitions, where common elements can be defined once and reused across multiple APIs.

YAML and JSON : The $ref keyword can be used in both YAML and JSON files, which are common formats for defining OpenAPI specifications. It is not limited to YAML files.

Location Flexibility : $ref can be defined at various levels within the YAML or JSON file, not necessarily at the root level. It can be used within objects, arrays, and other structures as needed.

Gatewayscript : While Gatewayscript can include external files, it does not use the $ref keyword in the same way as OpenAPI specifications. Gatewayscript has its own mechanisms for including and referencing external scripts.

References :

IBM API Connect documentation on OpenAPI specifications and the use of $ref.

General principles of API design and modularization using OpenAPI.

To monetize a Product in API Connect, you must first configure a billing integration resource for the Provider organization. This resource defines the payment gateway or other payment method that will be used to process payments for API subscriptions. Once a billing integration resource is configured, you can create paid plans for your Products and enable billing for those plans.

References:

IBM API Connect: Monetizing APIs

IBM API Connect: Configuring Billing Integration Resources

API Properties : In IBM API Connect, API properties are configuration settings that can be used to customize the behavior of APIs. These properties can be defined at various levels, including the API, Product, and Catalog levels.

Catalog-Specific Values : A property can be assigned a specific value for each Catalog. This allows for different configurations and behaviors of the same API when deployed in different Catalogs. For example, an API might have different endpoint URLs or security settings in development, testing, and production environments.

Runtime Changes : While some properties can be modified at runtime, this is not a general rule for all API properties. The ability to change property values at runtime depends on the specific property and its configuration.

Pre-defined Properties : API properties can be both pre-defined and custom-defined. Pre-defined properties are provided by IBM API Connect, while custom properties can be created by API developers to suit specific needs.

Spaces and Properties : If Spaces are enabled, properties can indeed have Space-specific values. This allows for further granularity in configuration, enabling different settings within the same Catalog based on the Space.

References :

IBM API Connect documentation on API properties and their configurations.

Best practices for managing API properties in IBM API Connect.

OAuth Provider Customization : When customizing a native OAuth provider in IBM API Connect, certain configurations and policies can affect its readiness for immediate use.

TLS Profile Reference : Adding a policy that references a TLS (Transport Layer Security) profile introduces additional security configurations that need to be validated and applied. This process can delay the immediate readiness of the OAuth provider.

Impact of TLS Profiles : TLS profiles are used to secure communications and ensure data integrity and confidentiality. When a policy with a TLS profile reference is added, the system must ensure that the TLS settings are correctly configured and operational, which can take additional time.

Other Options :

Transform Policies : These are used to modify the request or response messages and do not inherently delay the readiness of the OAuth provider.

Grant Types : Adding grant types involves configuring the OAuth provider to support different methods of obtaining access tokens, which is a standard part of customization and does not delay readiness.

Logic Operators : Using logic operators in the assembly is related to the flow control of the API assembly and does not directly impact the readiness of the OAuth provider.

References :

IBM API Connect documentation and best practices for OAuth provider customization.

General principles of TLS and its impact on API security configurations.