We have now added support for multiple datetime formats in our PHP SDKs. The following formats are supported:
- RFC1123 Datetime:
Mon, 15 Jun 2009 20:45:30 GMT
- RFC3339 Datetime:
2016-03-13T12:52:32.123Z
- Unix Timestamp:
1480809600
We have now added support for multiple datetime formats in our PHP SDKs. The following formats are supported:
Mon, 15 Jun 2009 20:45:30 GMT
2016-03-13T12:52:32.123Z
1480809600
We have recently revamped our support for XML schema. This includes bug fixes (array types and optional properties were not catered in some cases, issues with circular references, etc.) and addition of missing features (Union of simple types, redefinition of schema types, etc.).
Our API editor and Code Generation engine now supports OAuth 2.0 for authentication in the generated SDKs.
OAuth 2 enabled SDKs will help developers in:
You can read more about OAuth 2.0 in APIMatic editor and Code Generation engine here.
You can now set Composer Package Name for PHP SDKs being generated.
This will affect the name
generated in the composer.json
file. Leaving it empty will generate the a fallback package name based on your API name.
APIMatic Code Generation engine now supports polymorphic responses with the help of a discriminator field.
Check out the Discriminator documentation to get started.
There was an issue in code generation for PHP SDKs where the model classes (custom types) had fields with incorrect
PHP typehints. This lead to the JsonMapper
mapping responses incorrectly to models during deserialization. However, this
only occurred when a model had fields that were described as optional in the API description and no default value was provided.
Re-generate your PHP SDK to get the fix.
APIMATIC's PHP SDKs are now compliant with the PSR-2 Coding Style Guide
Re-generate your PHP SDKs now for the new changes.
A bug in PHP SDKs being generated lead to custom Error Exception Models not being deserialized properly from the response when an API error occurred. This was caused by an error in the unbox()
function in the custom Exception class. It has now been fixed.
If you were using custom Error Exceptions, then please re-generate your PHP SDKs to get the fix.
A logical error in the PHP SDKs being generated lead to a variable, _httpContext
, being undefined in some cases. This resulted in a Fatal error when an APIException
was expected to be thrown.
Please regenerate your PHP SDK to get the bug fix.
You can now use multiple base URLs in your API description using the new Server Configuration. This feature allows you to