Answer
No — a field-length limit like this is almost always a genuine underlying Oracle column-length constraint on whichever table/LU the data ultimately lands in, and a BizAPI (or any integration layer) can't override the length of the actual database column it's writing to. Before assuming it's adjustable, check the defined length of that specific column in Oracle for the LU the address data resolves to — if it really is capped there, the limit needs to be treated as a genuine data constraint to design the integration around, rather than a configurable API setting.